[Bug 97901] Far Cry 2 (wine) crashes on level load

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Sep 26 10:54:26 UTC 2016


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

--- Comment #1 from Eero Tamminen <eero.t.tamminen at intel.com> ---
(In reply to bartos.petr from comment #0)
> on Intel HD Graphics 5500 (Broadwell GT2) with with git version of mesa
> (installed from https://copr.fedorainfracloud.org/coprs/griever/mesa-git/) 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
> https://bugs.freedesktop.org/show_bug.cgi?id=74868 (leaking bytecode on
> shader compile failure) or this
> (https://bugs.freedesktop.org/show_bug.cgi?id=29170)

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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20160926/1d2abb9e/attachment.html>


More information about the intel-3d-bugs mailing list