https://bugs.winehq.org/show_bug.cgi?id=46626
--- Comment #7 from Nikolay Sivov bunglehead@gmail.com --- (In reply to Anastasius Focht from comment #6)
It's unfortunate that https://source.winehq.org/git/wine.git/commit/ 9b90cfc2817e171e7a9698605deecc3438712af8 had no corresponding Bugzilla bug report otherwise the issue could have been properly analysed/explained earlier.
I still see many times patches committed that appear to be out of the blue without any background information what they ought to fix. Sometimes it's possible to guess .. many times not. I don't know why it's so hard to create tracking bugs referring to real world apps/games. This lack of traceability causes later additional efforts on figuring out things in case of regressions and/or do really proper fixes.
The issue was about Uplay hanging on initial window creation, in resource calls from early window initialization (call originated from user32 itself as I remember). I was testing this on Debian, with Debian-provided compiler and tools, with default build flags.
It should be possible to reproduce this with current versions too I think.