[Bug 47351] New: World of Warcraft still crashes at launch
https://bugs.winehq.org/show_bug.cgi?id=47351 Bug ID: 47351 Summary: World of Warcraft still crashes at launch Product: Wine Version: 4.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: berillions(a)gmail.com Regression SHA1: 13e11d3fcbcf8790e031c4bc52f5f550b1377b3b Distribution: Gentoo Created attachment 64686 --> https://bugs.winehq.org/attachment.cgi?id=64686 GetTickCount hack for WoW ... again Hello, I still have a crash at launch with World of Warcraft (i did not try with others Blizzard games). When i launch the game, it crash with a Blizzard error 138 like this : "ACCESS_VIOLATION : error 138: ERROR #138 (0x8510008a) Fatal exception! The instruction at "0x0000000000000000" referenced memory at "0x0000000000000000". The memory could not be "executed". With the attached hack, the game launches correctly without crash. -- 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=47351 Berillions <berillions(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|World of Warcraft still |World of Warcraft still |crashes at launch |crashes at launch with | |Wine-4.10 -- 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=47351 Sveinar Søpler <cybermax(a)dexter.no> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax(a)dexter.no --- Comment #1 from Sveinar Søpler <cybermax(a)dexter.no> --- (In reply to Berillions from comment #0)
Created attachment 64686 [details] GetTickCount hack for WoW ... again
Hello,
I still have a crash at launch with World of Warcraft (i did not try with others Blizzard games). When i launch the game, it crash with a Blizzard error 138 like this : "ACCESS_VIOLATION : error 138: ERROR #138 (0x8510008a) Fatal exception! The instruction at "0x0000000000000000" referenced memory at "0x0000000000000000". The memory could not be "executed".
With the attached hack, the game launches correctly without crash.
You would not happen to be using "Clock Monotonic Raw" patch from TKG patches? https://github.com/Tk-Glitch/PKGBUILDS/blob/master/wine-tkg-git/wine-tkg-pat... -- 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=47351 Berillions <berillions(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Berillions <berillions(a)gmail.com> --- I confirm that using "Clock Monotonic Raw" patch from TKG patches caused the issue. -- 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=47351 André H. <nerv(a)dawncrow.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED CC| |nerv(a)dawncrow.de --- Comment #3 from André H. <nerv(a)dawncrow.de> --- closing invalid -- 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 (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla