<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Far Cry 2 (wine) crashes on level load" href="https://bugs.freedesktop.org/show_bug.cgi?id=97901#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Far Cry 2 (wine) crashes on level load" href="https://bugs.freedesktop.org/show_bug.cgi?id=97901">bug 97901</a> from <a class="email" href="mailto:eero.t.tamminen@intel.com" title="Eero Tamminen <eero.t.tamminen@intel.com>"> Eero Tamminen</a> <pre>(In reply to bartos.petr from <a href="show_bug.cgi?id=97901#c0">comment #0</a>) > on Intel HD Graphics 5500 (Broadwell GT2) with with git version of mesa > (installed from <a href="https://copr.fedorainfracloud.org/coprs/griever/mesa-git/">https://copr.fedorainfracloud.org/coprs/griever/mesa-git/</a>) I > found problem with Far Cry 2. Game starts, I can navigate menus, however > game crashes on loading screen. In console there is either: > > err:d3d:wined3d_debug_callback 0xa6d7670: "GL_OUT_OF_MEMORY in > glCompressedTexSubImage2D" > > many times or: > > err:d3d:wined3d_debug_callback 0xa9189a8: "GL_OUT_OF_MEMORY in > glMapBufferRange(map failed) Game crash is likely due to the out of memory errors with the GL calls. > many times. with INTEL_DEBUG=perf I see many: > > SIMD16 shader failed to compile: FS compile failed: Failure to register > allocate. Reduce number of live scalar values to avoid this. > Multi-LOD fast clear - giving up (1024x2048x11). This doesn't cause reliability issues. > There are no errors in dmesg. > > I did not play this game for some time, but I know for sure it was working > on my machine before with same graphics setting. When I set everything to > low details, game starts, but I did not yet found which setting is causing > troubles. When I set back all settings to previous values in game, I can > play for some time before game crashes. Did things start crashing after Mesa update, or Wine update? This issue could be excessive GL resource usage from newer Wine version too. > Maybe it is somehow related to this > <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - r600g: Diablo III Crashes After a few minutes" href="show_bug.cgi?id=74868">https://bugs.freedesktop.org/show_bug.cgi?id=74868</a> (leaking bytecode on > shader compile failure) or this > (<a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED FIXED - [regression] Far Cry (in Wine) hangs on level load" href="show_bug.cgi?id=29170">https://bugs.freedesktop.org/show_bug.cgi?id=29170</a>) First one is in unrelated part of code, and second is so old that it's not anymore relevant either. The instructions for Valgrind usage should be fine though. Valgrind --tool=memcheck and --tool=massif outputs of the use-case would be useful.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>