From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109534] Crash in Minecraft due to a swp[chan] assertion fail in src/gallium/drivers/r600/sb/sb_ir.cpp alu_packed_node::update_packed_items
Date: Sun, 25 Aug 2019 19:55:20 +0000 [thread overview]
Message-ID: <bug-109534-502-6lDmitwAAk@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-109534-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 241 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109534
--- Comment #7 from vanyasmart@gmail.com ---
No, sorry. Still happening with Oracle JRE, but more rarely.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1168 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-08-25 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 19:49 [Bug 109534] Crash in Minecraft after a swp[chan] assertion fail since the last debian upgrade bugzilla-daemon
2019-02-02 19:53 ` [Bug 109534] Crash in Minecraft after a swp[chan] assertion fail since the last debian upgrade of mesa bugzilla-daemon
2019-02-02 21:58 ` [Bug 109534] Crash in Minecraft due to a swp[chan] assertion fail in src/gallium/drivers/r600/sb/sb_ir.cpp alu_packed_node::update_packed_items bugzilla-daemon
2019-02-08 21:15 ` bugzilla-daemon
2019-02-21 22:11 ` bugzilla-daemon
2019-03-09 13:24 ` bugzilla-daemon
2019-03-10 9:11 ` bugzilla-daemon
2019-03-30 19:56 ` bugzilla-daemon
2019-08-25 19:49 ` bugzilla-daemon
2019-08-25 19:55 ` bugzilla-daemon [this message]
2019-09-18 19:26 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-109534-502-6lDmitwAAk@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.