<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [i965 on HD4600 Haswell] xcom switch to ingame cinematics cause segmentation fault" href="https://bugs.freedesktop.org/show_bug.cgi?id=97225#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [i965 on HD4600 Haswell] xcom switch to ingame cinematics cause segmentation fault" href="https://bugs.freedesktop.org/show_bug.cgi?id=97225">bug 97225</a> from <a class="email" href="mailto:mattst88@gmail.com" title="Matt Turner <mattst88@gmail.com>"> Matt Turner</a> <pre>(In reply to _archuser_ from <a href="show_bug.cgi?id=97225#c0">comment #0</a>) > Specific parts of xcom: enemy unknown cause a segfault in i965_dri.so > (64bit), last known mesa version to work without segfault was 11.2.2-1 (arch > package from Feb 11, if i965_dri.so loaded via LIBGL_DRIVERS_PATH, it still > works). > Xcom seems to to some specific things when switching to ingame cinematics > (e.g. after first mission transition, some stuff near endgame etc.) and only > crashes on these parts , rest of the game seems to work fine. > > apitrace / glretrace produce traces that always crash semi-randomly during > replay and are unusable for me atm. If the trace was used to get the backtrace, I suspect it'll be useful to me. Could you post it somewhere? > Trace shows recursive calls to nir_phi_builder_value_get_block_def ? -> > stack overflow causing SEGSEGV ? That looks plausible. > Not a C programmer here, took some time to set this up to work at all. I'm very appreciative!</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>