https://bugs.winehq.org/show_bug.cgi?id=58044
Bug ID: 58044 Summary: Realm Grinder freezes/crashes after a very long run Product: Wine Version: 10.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs@winehq.org Reporter: galtgendo@o2.pl Distribution: ---
Created attachment 78299 --> https://bugs.winehq.org/attachment.cgi?id=78299 output of two failed runs
This I strongly suspect is a regression, yet I can't really pin down the time when this started happening. The problem happens with little to no human interaction, yet the timeframes make it unreasonable to actively reproduce. I suspect it started around 10.0 release, but with a -/+ 2 months margin (so close to useless).
Anyway, what's the problem ?
If Realm Grinder is run for long enough (but 'long enough' here is measured in *days*), it tends to eventually either freeze with a completely black window or crash with an X server error.
The attachment has output of two such runs, second chunk is when it just froze, the first when it crashed.
'fixme:d3d:swapchain_blit_gdi Using GDI present.' at the end of both seems to be the moment the problem triggers.
It seems to be some kind of a resource leak, but it doesn't affect any other apps running besides it, not even those run by wine.
No user action is really required to trigger this - I've seen it freeze after a desktop switch, I've seen it crash when the window was just displayed, but not really interacted with.
(Realm Grinder here is still at v4.2.27.0, though I'll likely update it shortly for Easter event)