https://bugs.winehq.org/show_bug.cgi?id=42805
Bug ID: 42805 Summary: World of Warcrafft 64 bit client freezes or glitches after some time Product: Wine Version: 2.0-rc6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: theodorstormgrade@googlemail.com Distribution: ---
The issue is that the 64bit client of World of Warcraft (not the 32bit client) freezes after some time or result in glitches like this [1]. Another glichtes is red shade over the screen with other colors changed. I tried a more recent version of wine with direct3d11 and the glitch occurred to. The bug trigger totally random sometimes it happens minutes after login, sometimes after hours. After a new patch bug don't occurs for a time.
For more reports of this bug just look at the application page of the app there are more users reporting this issue.
No dll overrides used, Windows Version is either XP or Windows 7 but it makes no difference (Blizzard detecs Linux anyway ;) )
https://dl.dropboxusercontent.com/u/172590784/wow/screenshots/WoWScrnShot_09... (look at the yellow tint of the scene)
The bug initially happened since the 1.9.x series as far as I remember and is some kind of an issue between a change of Blizzard and wine.
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #1 from Bjoern Bidar theodorstormgrade@googlemail.com --- Created attachment 57835 --> https://bugs.winehq.org/attachment.cgi?id=57835 log file with fixme+all,err+all
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #2 from Bjoern Bidar theodorstormgrade@googlemail.com --- disabled __GL_THREADED_OPTIMIZATION makes no difference
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #3 from Bjoern Bidar theodorstormgrade@googlemail.com --- Created attachment 57838 --> https://bugs.winehq.org/attachment.cgi?id=57838 log file with fixme+all,err+all.warn+all
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #4 from Bjoern Bidar theodorstormgrade@googlemail.com --- I noticed when ever the game freezes enterily or just for second wine spams: warn:winsock:WS2_recv_base -> ERROR 10035
Maybe this is related somewhere?
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #5 from Bjoern Bidar theodorstormgrade@googlemail.com --- Created attachment 57844 --> https://bugs.winehq.org/attachment.cgi?id=57844 logfile with fixme+all,err+all,warn+winsock,trace+winsock
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #6 from Bjoern Bidar theodorstormgrade@googlemail.com --- Created attachment 57846 --> https://bugs.winehq.org/attachment.cgi?id=57846 logfile with fixme+all,err+all,warn+winsock,trace+winsock (32bit client)
https://bugs.winehq.org/show_bug.cgi?id=42805
PeterG peter.g.anderson@live.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |peter.g.anderson@live.co.uk
--- Comment #7 from PeterG peter.g.anderson@live.co.uk ---
From your attachments, the wrapper script you are using makes several
references to __GL_THREADED_OPTIMIZATION=1
The correct usage is __GL_THREADED_OPTIMIZATIONS=1.
If you are using wine-staging with CSMT enabled, it may be advisable to remove these altogether, along with references to
LD_PRELOAD='libpthread.so.0 libGL.so.1'.
Using CSMT with these enabled can cause problems with many games and apps.
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #8 from Bjoern Bidar theodorstormgrade@googlemail.com --- But than is would affect the 32bit client too or hot? I'll try to disable it again. How can I provide better debug information?
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #9 from Bjoern Bidar theodorstormgrade@googlemail.com --- Tried it again without __gl_threadeded_optimisations and it didn't changed anything
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #10 from Bjoern Bidar theodorstormgrade@googlemail.com --- I disabled csmt and got this error: err:ntdll:RtlpWaitForCriticalSection section 0x100a8 "../../../wine/dlls/ntdll/heap.c: main process heap section" wait timed out in thread 00c8, blocked by 00a2, retrying (60 sec)
This comes every 60s but with a different address
https://bugs.winehq.org/show_bug.cgi?id=42805
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #11 from winetest@luukku.com --- What do you think if bug 41166 is about the same issue? It has a short video clip (youtube) to demonstrate the issue.
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #12 from Bjoern Bidar theodorstormgrade@googlemail.com --- no its a different renderer.
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #13 from PeterG peter.g.anderson@live.co.uk --- Which wine version are you currently using and what is the version of your graphics driver?
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #14 from Bjoern Bidar theodorstormgrade@googlemail.com --- Hey I've found the issue: the issue is that when I build when with -march=native rather than with -march=generic the game freezes. I tried the latest wine staging and the regular wine. My progrezessor is a Intel i7 6900k (Broadwell EP). I'm using GCC 6.3.1 on Arch Linux
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #15 from Bjoern Bidar theodorstormgrade@googlemail.com --- Created attachment 57971 --> https://bugs.winehq.org/attachment.cgi?id=57971 output of ´gcc -march=native -v -Q --help=target´
output of ´gcc -march=native -v -Q --help=target´ to see what flags were used when building with -mtune=native.
https://bugs.winehq.org/show_bug.cgi?id=42805
Drew McRae winebugs@mcraes.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winebugs@mcraes.org
--- Comment #16 from Drew McRae winebugs@mcraes.org --- Created attachment 58285 --> https://bugs.winehq.org/attachment.cgi?id=58285 Output of `gcc -march=native -v -Q --help=target` for Ryzen
I'm having a similar issue with -march=native on my Ryzen 7 1800x using gcc 6.3.0 on Gentoo. I've had this with numerous versions of wine, but recent testing has been with 2.3, 2.5, and 2.8. When I changed my -march to haswell (as had been suggested for Ryzen CPUs before gcc 6), the crashes/freezes go away. I have attached my output of `gcc -march=native -v -Q --help=target` as well, hopefully that helps narrow things down.
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #17 from Bjoern Bidar theodorstormgrade@googlemail.com --- With wow too or with which application?
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #18 from Bjoern Bidar theodorstormgrade@googlemail.com --- Created attachment 58286 --> https://bugs.winehq.org/attachment.cgi?id=58286 diff -u gcc_native.txt gcc_haswell.txt &> gcc_diff_broadwell_haswell.diff
I wonder because I have a broadwell(-ep) cpu so haswell shouldn't bee that different but still for gcc their are see here.
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #19 from Drew McRae winebugs@mcraes.org --- My problem is with 64-bit Wow as well; specifically, it would crash or freeze (with a segfault, I believe) after about 10 seconds of running.
I did just get a few more freezes with haswell, but they were much later (I had been playing for 10 minutes or so), and they just spiked the CPU. I'm not sure if the problem is the same, since the symptoms are different, but I thought it worth mentioning.
https://bugs.winehq.org/show_bug.cgi?id=42805
Karol Fuksiewicz kfuks2@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kfuks2@gmail.com
--- Comment #20 from Karol Fuksiewicz kfuks2@gmail.com --- Hi, have the same problem... And why this bug is still not confirmed...
On World of Warcraft application page is also "fix" for this.
Commit that cause problem is: https://github.com/wine-compholio/wine-staging/commit/ee5545a45f164d640c9b1c... as Björn Bidar found.
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #21 from Karol Fuksiewicz kfuks2@gmail.com --- Hi, have the same problem... And why this bug is still not confirmed...
On World of Warcraft application page is also "fix" for this.
Commit that cause problem is: https://github.com/wine-compholio/wine-staging/commit/ee5545a45f164d640c9b1c... as Björn Bidar found.
https://bugs.winehq.org/show_bug.cgi?id=42805
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
--- Comment #22 from Sebastian Lackner sebastian@fds-team.de --- (In reply to Karol Fuksiewicz from comment #21)
Hi, have the same problem... And why this bug is still not confirmed...
On World of Warcraft application page is also "fix" for this.
Commit that cause problem is: https://github.com/wine-compholio/wine-staging/commit/ ee5545a45f164d640c9b1cd6575a5645afaeb4a9 as Björn Bidar found.
You are mixing up two different bugs. This specific bug was reported with Wine 2.0 and is related to Wine compilation flags (-march=native).
The link you provided is a Wine Staging regression (see bug 43195), only affects Wine Staging 2.10, and is already fixed in current git. Please upgrade to 2.11 if this is the problem you encounter.
https://bugs.winehq.org/show_bug.cgi?id=42805
--- Comment #23 from Karol Fuksiewicz kfuks2@gmail.com --- (In reply to Sebastian Lackner from comment #22)
(In reply to Karol Fuksiewicz from comment #21)
Hi, have the same problem... And why this bug is still not confirmed...
On World of Warcraft application page is also "fix" for this.
Commit that cause problem is: https://github.com/wine-compholio/wine-staging/commit/ ee5545a45f164d640c9b1cd6575a5645afaeb4a9 as Björn Bidar found.
You are mixing up two different bugs. This specific bug was reported with Wine 2.0 and is related to Wine compilation flags (-march=native).
The link you provided is a Wine Staging regression (see bug 43195), only affects Wine Staging 2.10, and is already fixed in current git. Please upgrade to 2.11 if this is the problem you encounter.
ok, sorry then, must missunderstood smth'...
https://bugs.winehq.org/show_bug.cgi?id=42805
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #24 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-5.11?