https://bugs.winehq.org/show_bug.cgi?id=54436
--- Comment #7 from Austin English austinenglish@gmail.com --- (In reply to kolAflash from comment #6)
(In reply to Erich E. Hoover from comment #5)
The variety of symptoms here and what you're describing makes me think that the app uses stack-allocated memory and the stack is full.
How can this be influenced by the changes between wine-7.8 and wine-8.0 ?
Why did the stack not become full with wine <= 7.8 ?
Well, given that this bug is a regression, it sounds like some commit introduced a difference in memory allocation (or potentially a memory leak) that caused the crash you're seeing.
If you use native d3x9, does it not crash at deaf0891b096628cf99e58834c39a45a6c99c54c, but does crash at fd8e52b4e7604e85924afd70482282efd583e74c? If so, a bisect (with native d3dx9) between those two commits should identify the problem.
If that is not the case, then I'd suggest trying 4a98b07c4bcc35a698448261478ba856c149cbea, then cherry-pick deaf0891b096628cf99e58834c39a45a6c99c54c and/or fd8e52b4e7604e85924afd70482282efd583e74c and see how that behaves.