<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:jfonseca@vmware.com" title="Jose Fonseca <jfonseca@vmware.com>"> <span class="fn">Jose Fonseca</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - XCOM: Enemy Unknown Causes lockup"
href="https://bugs.freedesktop.org/show_bug.cgi?id=80419">bug 80419</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>brianp@vmware.com, jfonseca@vmware.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - XCOM: Enemy Unknown Causes lockup"
href="https://bugs.freedesktop.org/show_bug.cgi?id=80419#c88">Comment # 88</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - XCOM: Enemy Unknown Causes lockup"
href="https://bugs.freedesktop.org/show_bug.cgi?id=80419">bug 80419</a>
from <span class="vcard"><a class="email" href="mailto:jfonseca@vmware.com" title="Jose Fonseca <jfonseca@vmware.com>"> <span class="fn">Jose Fonseca</span></a>
</span></b>
<pre>(In reply to Kamil Páral from <a href="show_bug.cgi?id=80419#c87">comment #87</a>)
<span class="quote">> The apitrace developer patched glretrace, so that it no longer crashes
> during replay. He says it's a bug inside XCOM. He also says the problem
> might likely cause the radeonsi driver crash as well. See his comment here:
> <a href="https://github.com/apitrace/apitrace/issues/407#issuecomment-166619366">https://github.com/apitrace/apitrace/issues/407#issuecomment-166619366</a>
>
> (If this indeed turns out to be an XCOM bug, it would be nice if we could
> put some safeguards into the driver and didn't crash for invalid commands,
> but I'm saying that as someone who knows exactly zero about gpu driver
> programming).</span >
Yep. We could add a new drirc hack for ignoring the start/end params of
glDrawRangeElementsBaseVertex for applications like XCOM, ie, assume 0..~0.
XCOM is not unique here -- we've seen this happening on a Direct3D9 once at
VMware. It looks like some of the proprietary OpenGL/Direct3D drivers out
there simply outright ignore the min/max index hints.</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>