From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 35942] New: Crash in World of Warcraft
Date: Mon, 4 Apr 2011 01:16:53 -0700 (PDT) [thread overview]
Message-ID: <bug-35942-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=35942
Summary: Crash in World of Warcraft
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: rankincj@googlemail.com
World of Warcraft is crashing again, after a few minutes fishing in Dalaran's
fountain.
After reverting as far back as:
commit 381d32af74e305041b5e75930a32795db94e0e15
Author: Tom Stellard <tstellar@gmail.com>
Date: Sat Apr 2 23:14:12 2011 -0700
Revert "r300/compiler: Remove obsolete compiler passes"
This reverts commit 9f013a8233197d4a0482661cb37cfeac1a61b804.
These passes are still need for non-GLSL paths like g3dvl and ARB
programs.
I was able to fish in Dalaran's fountain for several hours, although the crash
was still present when I'd only reverted as far back as:
commit 437c748bf5072d2bded77a00c74c51cdb8b510e5
In between these two commits is c35572352e3e92683988ee8d151b47f4190d62f9, which
I have not tested.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-04-04 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 8:16 bugzilla-daemon [this message]
2011-04-04 15:04 ` [Bug 35942] Crash in World of Warcraft bugzilla-daemon
2011-04-04 18:12 ` bugzilla-daemon
2011-04-04 18:40 ` bugzilla-daemon
2011-04-04 21:00 ` bugzilla-daemon
2011-04-04 23:36 ` bugzilla-daemon
2011-04-08 19:40 ` 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-35942-502@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox