<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - WoW crashes in OpenGL mode with Mesa, but not with NVIDIA blob"
href="https://bugs.freedesktop.org/show_bug.cgi?id=91600">91600</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>WoW crashes in OpenGL mode with Mesa, but not with NVIDIA blob
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Drivers/Gallium/r600
</td>
</tr>
<tr>
<th>Assignee</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>rankincj@googlemail.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>dri-devel@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>Created <span class=""><a href="attachment.cgi?id=117619" name="attach_117619" title="WINEDEBUG trace, including R600 shaders">attachment 117619</a> <a href="attachment.cgi?id=117619&action=edit" title="WINEDEBUG trace, including R600 shaders">[details]</a></span>
WINEDEBUG trace, including R600 shaders
Hardware tested: Linux x64, both HD4890 and HD6450
World of Warcraft (OpenGL mode) has been crashing ever since it upgraded itself
to 6.2. I had assumed that it was a bug in the WoW client, until I noticed that
WoW did not crash on a machine running with the NVIDIA binary blob.
I have executed WoW using the following command:
$ R600_DEBUG=fs,vs,gs,ps,cs WINEDEBUG=+opengl,+wgl,seh ./Wow-64.exe
And it appears that WoW is throwing an exception in a glLoadMatrix() operation:
trace:opengl:glCallList (1)
trace:opengl:glLoadMatrixf (0x22f610)
trace:seh:raise_exception code=c0000005 flags=0 addr=(nil) ip=0 tid=0027
trace:seh:raise_exception info[0]=0000000000000000
trace:seh:raise_exception info[1]=0000000000000000
trace:seh:raise_exception rax=0000000006e9d2c0 rbx=0000000006e9ffd0
rcx=0000000000009117 rdx=0000000000000000
trace:seh:raise_exception rsi=00000001413696b1 rdi=0000000006e9d2c0
rbp=000000000022fa60 rsp=000000000022f898
trace:seh:raise_exception r8=000000000000000a r9=000000000022f610
r10=00007f2857d369f6 r11=000000000022f7f0
trace:seh:raise_exception r12=00000000001b6b06 r13=0000000000000000
r14=00007fffff7e8000 r15=00007ffd34f83da0
trace:seh:RtlVirtualUnwind type 1 rip 1400de519 rsp 22f8a0
trace:seh:dump_unwind_info **** func de4d0-de5aa
trace:seh:dump_unwind_info unwind info at 0x1412e21ac flags 0 prolog 0x6 bytes
function 0x1400de4d0-0x1400de5aa
trace:seh:dump_unwind_info 0x6: subq $0x20,%rsp
trace:seh:dump_unwind_info 0x2: pushq %rbx
trace:seh:RtlVirtualUnwind type 1 rip 1400d0ec9 rsp 22f8d0
trace:seh:dump_unwind_info **** func d0e70-d0ef8
I don't know how to debug this any further; the more flags I add to WINEDEBUG,
the less likely WoW is to do *anything* (i.e. "run at all"). Raising this as a
means of requesting more ideas.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>