[Bug 46891] New: Memory Access Error in World of Warcraft 8.1.29814
https://bugs.winehq.org/show_bug.cgi?id=46891 Bug ID: 46891 Summary: Memory Access Error in World of Warcraft 8.1.29814 Product: Wine-staging Version: unspecified Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: blocker Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: juergen.sauer(a)automatix.de CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com Distribution: --- Created attachment 63967 --> https://bugs.winehq.org/attachment.cgi?id=63967 crashed app debug dialog Battle.net.exe works as expected. Patching Wow works also fine. Entering the Game works. Selection the Char and Menue Access outside the game works. But entering a Realm end in an Error #132 of Wow.exe, which shows up if the exe code tries to access illegal adress segments. -- 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=46891 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|blocker |normal CC| |dark.shadow4(a)web.de --- Comment #1 from Fabian Maurer <dark.shadow4(a)web.de> --- Not a blocker. Does this only affect wine-staging or also vanilla wine? -- 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=46891 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be --- Comment #2 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Possible duplicate of bug 46416. Do you use vkd3d/directx12? -- 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=46891 --- Comment #3 from juergen.sauer(a)automatix.de --- No. I do not use vkd3d/directx12. As I can see, the problem must exist Wine-staging 4.3.1 ... 4.4 I tried 4.2.1 staging, thus is working. In game I can chose "DirectX 11 Legacay", this works fast performant. (1080p @ 40 fps). Changing to "DirectX 11" (NO LEGACY) fps falls down to 1..3 fps. -- 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=46891 --- Comment #4 from juergen.sauer(a)automatix.de --- (In reply to Fabian Maurer from comment #1)
Not a blocker. Does this only affect wine-staging or also vanilla wine?
wine-staging, current has the bug. staging 4.2.1 has not. -- 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=46891 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #5 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with vanilla wine-5.14? -- 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=46891 --- Comment #6 from juergen.sauer(a)automatix.de --- Do not know. On daily use case "WowClassic.exe" wine staging 5.9 is really fine. But 5.14 fails to start the game at 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla