https://bugs.winehq.org/show_bug.cgi?id=42126
Ken Thomases ken@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|regression | Regression SHA1|1df961bd3d1a5d4d4badfe364ca | |51e9f6cc88fd3 |
--- Comment #9 from Ken Thomases ken@codeweavers.com --- (In reply to Jeff Zaroyko from comment #8)
(In reply to Ken Thomases from comment #7)
Thanks again. While I analyze the log, can you try one more thing for me? Revert the commit but then set VideoMemorySize=1536 and run without logging. Does the program still crash?
Reverted the commit, set VideoMemorySize=1536 - It crashes the same way as the original report.
OK, thanks for checking that. I'm going to remove my commit and the regression tag. The only role my commit had was to properly determine the amount of VRAM. As you've determined, if the proper size had been set via the registry, the crash would have happened even before my commit.
Probably, this is a game bug and it just can't deal with the high amount of VRAM. The log shows it's in a loop of checking formats. I'm not sure why it doesn't crash when logging. That may indicate another game bug with an uninitialized variable such that Wine doing different things (like logging) leaves different leftover data in the game's variable and causes it to change behavior. It's also possible the logging just slowed it down and it would have eventually run out of memory and crashed given enough time (and disk space for the log).
It is possible that this is a bug in Wine (ddraw or wined3d), but I doubt it.