[Bug 80419] XCOM: Enemy Unknown Causes lockup

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=80419

Jose Fonseca <jfonseca at vmware.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |brianp at vmware.com,
                   |                            |jfonseca at vmware.com

--- Comment #88 from Jose Fonseca <jfonseca at vmware.com> ---
(In reply to Kamil Páral from comment #87)
> 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:
> https://github.com/apitrace/apitrace/issues/407#issuecomment-166619366
> 
> (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).

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.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20151222/f1f6c46b/attachment.html>