https://bugs.winehq.org/show_bug.cgi?id=57109
--- Comment #4 from Pedro M Sanches pedrodarch15b@gmail.com --- Created attachment 77033 --> https://bugs.winehq.org/attachment.cgi?id=77033 WINEDEBUG=+server output
After figuring out that this issue is reproducible by launching Max on it's own, I have been able to successfully start it by erasing the contents of it's Settings folder. If those files are not present, Max starts just fine on any version of Wine newer than 9.12. This may indicate that I now know what I need to get a more useful result out of another regression test, but at the time I'm writing this, I have not slept.
Instead I was poking around with WINEDEBUG variables on stuff that to me was seemingly causing issues. After a few dozen seconds of having a blank window titled "Max is Starting Up" or something like that I could observe a single thread spamming sequences of lines like this on wine stderr:
0148: select( flags=2, cookie=7ffffe5fe830, timeout=+0.0009915, size=8, prev_apc=0000, result={}, data={WAIT,handles={00b4}}, contexts={} ) 0148: select() = PENDING { apc_handle=0000, signaled=0, call={}, contexts={} } 0148: *wakeup* signaled=TIMEOUT 0148: select( flags=2, cookie=7ffffe5fe830, timeout=+0.0009916, size=8, prev_apc=0000, result={}, data={WAIT,handles={00b4}}, contexts={} ) 0148: select() = PENDING { apc_handle=0000, signaled=0, call={}, contexts={} } 0148: *wakeup* signaled=TIMEOUT ...
This wasn't happening prior to Wine 9.11.
I am not sure if this is of any help. Full log is attached. I've had to compress it since it's more than 10 megs in size.