https://bugs.winehq.org/show_bug.cgi?id=54436
--- Comment #10 from kolAflash kolAflash@kolahilft.de --- Created attachment 74034 --> https://bugs.winehq.org/attachment.cgi?id=74034 "Star Trek: Armada II" GL_OUT_OF_MEMORY crashlog
Now I have had the same problem with another game. I attached the log.
01b4:err:d3d:wined3d_debug_callback 00814310: "GL_OUT_OF_MEMORY in glMapBufferRange(map failed)".
Star Trek: Armada II https://appdb.winehq.org/objectManager.php?sClass=application&iId=2115
I have had this problem recently 2 times. "Star Trek: Armada II" never ran stable with wine-8.1 for more than 15 minutes. But I was able to run it without problems for more than 90 minutes using wine-7.0.
On the other hand I have played a lot of "Diablo III" and "StarCraft II" in the recent months. And they ran completely stable. I have always used the most recent wine version in the last month (so a lot of wine >= 7.9). So I guess these games are not affected at all.
Diablo III (mostly played with Wine OpenGL based DirectX renderer) https://appdb.winehq.org/objectManager.php?sClass=version&iId=29952
StarCraft II (mostly played with DXVK) https://appdb.winehq.org/objectManager.php?sClass=version&iId=20882
The main difference that comes to my mind is, that "Diablo III" and "StarCraft II" these are 64 bit applications. While "Star Trek: Armada II" and "Command & Conquer 3: Tiberium Wars" are 32 bit applications.
---> Is this problem maybe something about running 32 bit games on system with a lot of GPU memory?
Remember, "Command & Conquer 3: Tiberium Wars" runs fine on my notebooks with a maximum of 2048 MB of GPU memory. But the game crashes on my desktop computer with 8192 MB of GPU memory.