https://bugs.winehq.org/show_bug.cgi?id=53372
--- Comment #2 from Patrick Hibbs hibbsncc1701@gmail.com --- Created attachment 72774 --> https://bugs.winehq.org/attachment.cgi?id=72774 MA applied OOM No crash console log
I applied the MA locally and retested it. Although the critical section errors no longer occur in the logs, the game is still unstable.
With the MA applied, the game won't even start occasionally. Deadlocking around D3D device init before the application window is generated.
When the game does start, it can occasionally crash at random (OOM error) where it didn't before. (Title screen, Campaign map before a battle, During a battle)
Additionally, I've had four test attempts that generated a GL OOM error during the return to the campaign map (a common point of failure) but did *not* cause a crash. Instead the game successfully reached the campaign map. Seemingly without issue (no UI / graphical glitches) and the current session could even be saved normally. The only indication of a problem was the console spewing GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT errors on every frame. (I've attached the complete console log from one of these four attempts.)
I've tried to get a d3d log for the non-fatal OOM error, but the game is very slow while doing so and I've yet to succeed. The last attempt ended with a crash during a battle and wound up being 311.7MB compressed / 30.3GB uncompressed. I could upload it if desired.