[Bug 50614] New: World of Warcraft Retail (WoW) crashes with 6.1-staging
https://bugs.winehq.org/show_bug.cgi?id=50614 Bug ID: 50614 Summary: World of Warcraft Retail (WoW) crashes with 6.1-staging Product: Wine Version: 6.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: blue-t(a)web.de Distribution: --- Created attachment 69303 --> https://bugs.winehq.org/attachment.cgi?id=69303 console version With the recent 6.1-staging release the game doesn't reach the login screen and hangs up with the famous #132 error "fatal exception" --------------------------- Wow --------------------------- This application has encountered a critical error: ERROR #132 (0x85100084) Fatal exception! ProcessID: 32 ThreadID: 36 Exception: ACCESS_VIOLATION The instruction at "0x000000018000396a" referenced memory at "0x0000000000000000". The memory could not be "read". Press OK to terminate the application. --------------------------- OK --------------------------- -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50614 --- Comment #1 from Ker noa <blue-t(a)web.de> --- Without wine-stagings ntdll-NtAlertThreadByThreadId/ the game starts again and we are back to a low fps game with various graphic bugs. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50614 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |-unknown Product|Wine |Wine-staging CC| |leslie_alistair(a)hotmail.com | |, z.figura12(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50614 Steve Ebey <eaglecomputers.ok(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eaglecomputers.ok(a)gmail.com --- Comment #2 from Steve Ebey <eaglecomputers.ok(a)gmail.com> --- Bug appears tied to your distro, no problems with game play in Fedora 33. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50614 Maia Everett <maia(a)everett.one> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maia(a)everett.one --- Comment #3 from Maia Everett <maia(a)everett.one> --- Happened to me as well on Ubuntu 20.04 with wine-staging 6.1 from the winehq repository. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50614 Jen <garputhefork(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |garputhefork(a)gmail.com --- Comment #4 from Jen <garputhefork(a)gmail.com> --- Question for those for whom WoW with wine-staging 6.1 is working. What version of glibc are you using? Slackware-current updated from 2.32 to 2.33, and WoW started crashing for me. Yesterday it worked, but today it doesn't. Other WINE applications are fine. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50614 malic <malicorne(a)chez.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |malicorne(a)chez.com --- Comment #5 from malic <malicorne(a)chez.com> --- Confirming issue with both 6.1 and 6.2 on Ubuntu 20.04 up to date. Downgrading to 6.0 make it work fine. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50614 --- Comment #6 from Ker noa <blue-t(a)web.de> --- (In reply to Jen from comment #4)
Question for those for whom WoW with wine-staging 6.1 is working. What version of glibc are you using? Slackware-current updated from 2.32 to 2.33, and WoW started crashing for me. Yesterday it worked, but today it doesn't. Other WINE applications are fine.
2.32-ubuntu3 is running here -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50614 --- Comment #7 from Ker noa <blue-t(a)web.de> --- (In reply to Ker noa from comment #6)
(In reply to Jen from comment #4)
Question for those for whom WoW with wine-staging 6.1 is working. What version of glibc are you using? Slackware-current updated from 2.32 to 2.33, and WoW started crashing for me. Yesterday it worked, but today it doesn't. Other WINE applications are fine.
2.32-ubuntu3 is running here
Which didn't work -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50614 --- Comment #8 from Zebediah Figura <z.figura12(a)gmail.com> --- Can you please check/bisect which patch from that patch set causes the crash? (There's a good chance it's 0012 [condition variables]). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50614 --- Comment #9 from Ker noa <blue-t(a)web.de> --- Maybe the compile process is messed up somewhere but i fail to recreate this properly. I have used 6.2-staging and 6.3-staging from the ubuntu groovy ppa and the game doesn't launch with it. But if i compile wine myself even applying all current staging patches seems to do it after a make clean, make j18. Maybe it is not that patchset after all. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50614 --- Comment #10 from Jen <garputhefork(a)gmail.com> --- (In reply to Ker noa from comment #9)
But if i compile wine myself even applying all current staging patches seems to do it after a make clean, make j18. Maybe it is not that patchset after all.
If I use the version of WINE I compiled myself (with mingw), WoW crashes. If I use Alien Bob's version of WINE, WoW doesn't crash. Looking at the build scripts, they're both similar, and to my knowledge we were both using the same version of mingw (Alien Bob's package.) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50614 --- Comment #11 from Jen <garputhefork(a)gmail.com> --- I think I have it figured it out, thanks to this test report: https://appdb.winehq.org/objectManager.php?sClass=version&iId=39861&iTesting... If WINE is compiled without vkd3d, WoW will crash. If dx11 is forced, it'll launch fine, even if dx11 is being used. This explains why Alien Bob's version worked and mine didn't. He compiled his with vkd3d support. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50614 --- Comment #12 from Ker noa <blue-t(a)web.de> --- I compiled my own 6.5 staging , regardless of wether i compile vk3d in or not, the whole thing works. As soon as i drop in the proton-vkd3d external dll, i am at the memory could not be read error. The whole thing is kind of weird. Leaving out staging ntalertthreadbythreadid seems to not play any role at the moment. How could we narrow this down? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=50614 Mike Lothian <mike(a)fireburn.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mike(a)fireburn.co.uk -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla