<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c128">Comment # 128</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 <a class="email" href="mailto:esmith@feralinteractive.com" title="Edwin Smith (Feral Interactive) <esmith@feralinteractive.com>"> Edwin Smith (Feral Interactive)</a> <pre>(In reply to Davin McCall from <a href="show_bug.cgi?id=80419#c127">comment #127</a>) > The comment above from Jose Fonseca (and follow up from Feral's Edwin Smith) > imply that the problem here is with the game calling > glDrawRangeElementsBaseVertex with bad start/end values, resulting in the > indices being out-of-range which is illegal per the GL spec, and implying > that this is what causes the crash. It might be useful to see what the Intel and/or r600 series drivers do as neither of these driver exhibit this crash in similar circumstances. The Intel Mesa driver might be best as this driver was fully supported from release without any reports of hangs post release. It's possible a comparison might help expose why RadeonSi behaves differently and narrow down the cause of the hang as it could be the root cause is hiding behind a more benign issue.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>