https://bugs.winehq.org/show_bug.cgi?id=38701
Bug ID: 38701 Summary: Stalker CoP crashes with error "GL_OUT_OF_MEMORY error generated. Failed to allocate memory for texture." Product: Wine Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: directx-d3d Assignee: wine-bugs@winehq.org Reporter: rief.the.dreamer@gmail.com Distribution: ---
Created attachment 51626 --> https://bugs.winehq.org/attachment.cgi?id=51626 The wine log containing the error lines
Playing Stalker Call of Pripyat plus the Misery Mod in wine both 1.7.38 and 1.7.44 with maximum details results in some kind of memory leak and a crash because no memory is left. The game crashes after 10-30 minutes. You can find the full log attached and apparently the two important lines are in the ogs are
err:d3d:wined3d_debug_callback 0x1956b0: "GL_OUT_OF_MEMORY error generated. Failed to allocate memory for texture.". err:d3d_texture:texture2d_prepare_texture >>>>>>>>>>>>>>>>> GL_OUT_OF_MEMORY (0x505) from glTexImage2D @ texture.c / 937
My system has a GTX 970 with 4GB of memory (I set 4GB graphical memory). I'm using NVIDIA drivers version 346.47.
The error seems similar to the one reported for dragon age 2 at https://www.winehq.org/pipermail/wine-bugs/2013-May/353719.html.
Please note that I have played Stalker Call of Pripyat with the Misery Mod many times thanks to wine. The only difference is that I have now a new computer and I'm running at maximum details instead of low. I have been able to finish the game previously. Let me know if you need more details and how to generate them.
https://bugs.winehq.org/show_bug.cgi?id=38701
Sergey Isakov isakov-sl@bk.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |isakov-sl@bk.ru
--- Comment #1 from Sergey Isakov isakov-sl@bk.ru --- This is well known missing support for DXTn textures. A plenty of such bugs already reported. --- fixme:d3dx:D3DXLoadSurfaceFromMemory Format conversion missing 0x35545844 -> 0x31545844
https://bugs.winehq.org/show_bug.cgi?id=38701
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal
--- Comment #2 from Ken Sharp imwellcushtymelike@gmail.com --- What version of Wine?
https://bugs.winehq.org/show_bug.cgi?id=38701
--- Comment #3 from rief rief.the.dreamer@gmail.com --- All the 1.7.x versions seems affected. I tried 1.7.33, 1.7.38, 1.7.44, 1.7.47. Still have to try 1.7.48 that I'm going to do today.
https://bugs.winehq.org/show_bug.cgi?id=38701
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #4 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-4.17?
https://bugs.winehq.org/show_bug.cgi?id=38701
robert.ayrapetyan@gmail.com robert.ayrapetyan@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |robert.ayrapetyan@gmail.com
--- Comment #5 from robert.ayrapetyan@gmail.com robert.ayrapetyan@gmail.com --- Still occurs with Wine 6.2 on FreeBSD x64 (Black Mirror 2), I thought it's nvidia + freebsd combo exclusive... It worked before with Intel HD on Wine 5.x though...
https://bugs.winehq.org/show_bug.cgi?id=38701
--- Comment #6 from Alex S iwtcex@gmail.com --- (In reply to robert.ayrapetyan@gmail.com from comment #5)
Seems like a run-of-the-mill address space exhaustion issue. See https://bugs.winehq.org/show_bug.cgi?id=44246#c3 and the following few comments.