[Bug 39490] New: Wine 1.7.53 crashes when starting StarCraft 2 (Wine 1.7.52 works fine)
https://bugs.winehq.org/show_bug.cgi?id=39490 Bug ID: 39490 Summary: Wine 1.7.53 crashes when starting StarCraft 2 (Wine 1.7.52 works fine) Product: Wine Version: 1.7.53 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kolAflash(a)kolahilft.de Distribution: --- Compiled Wine-1.7.52 (and all the versions before) myself. Works completely fine with StarCraft 2! Today compiled Wine-1.7.53 and it always crashes immediately and gives me the attached error on the shell. When reverting back to Wine-1.7.52, everything is OK again. The command I use to start StarCraft 2 and what happened: $ env LD_LIBRARY_PATH=~/opt/mesa3d/lib vblank_mode=0 WINEDLLOVERRIDES=winemenubuilder.exe=d force_s3tc_enable=true WINEARCH=win32 WINEPREFIX=~/wines/starcraft2/ ~/opt/wine/bin/wine ~/"wines/starcraft2/drive_c/Program Files/StarCraft II/StarCraft II.exe" err:wineboot:ProcessRunKeys Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2) fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub wine: Unhandled page fault on read access to 0x00000010 at address 0x7eab8a9a (thread 0029), starting debugger... X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 1 (X_CreateWindow) Resource id in failed request: 0x8200007 Serial number of failed request: 78 Current serial number in output stream: 82 Note: Compiled Mesa3D myself to (version 11.0.0). Tried running something simple with my standard system Mesa3D library. But that's also crashing... env WINEDLLOVERRIDES=winemenubuilder.exe=d WINEARCH=win32 WINEPREFIX=~/wines/starcraft2/ /home/moritz/opt/wine/bin/wine notepad wine: cannot find L"C:\\windows\\system32\\winemenubuilder.exe" err:wineboot:ProcessRunKeys Error running cmd L"C:\\windows\\system32\\winemenubuilder.exe -a -r" (2) wine: Unhandled page fault on read access to 0x00000010 at address 0x7eab8a9a (thread 0022), starting debugger... wine: Unhandled page fault on read access to 0x00000010 at address 0x7e7e3a9a (thread 0009), starting debugger... winedbg: Internal crash at 0x7bc5828d Interestingly Wine-1.7.53 is running fine with other WINEPREFIX'es. Guess it's maybe one of the following registry settings I made for the StarCraft 2 WINEPREFIX. I already compared the registry-settings in HKEY_CURRENT_USER\Software\Wine\Direct3D but they are the same in both WINEPREFIX'es. OS: openSUSE 13.2 (x86_64) CPU+GPU: Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz -- 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=39490 kolAflash <kolAflash(a)kolahilft.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Wine 1.7.53 crashes when |Wine 1.7.53 crashes when |starting StarCraft 2 (Wine |starting (Wine 1.7.52 works |1.7.52 works fine) |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=39490 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression CC| |sebastian(a)fds-team.de --- Comment #1 from Sebastian Lackner <sebastian(a)fds-team.de> --- The bug title is misleading, is only Starcraft 2 crashing, or there more affected applications? Could you please run a regression test, to find out which change in Wine is responsible for that crash? Take a look here for more information how to do such a regression test: http://wiki.winehq.org/RegressionTesting -- 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=39490 --- Comment #2 from kolAflash <kolAflash(a)kolahilft.de> --- (In reply to Sebastian Lackner from comment #1)
The bug title is misleading, is only Starcraft 2 crashing, or there more affected applications?
As said, notepad is also crashing. It seems to be more about the WINEPREFIX than about the program which is running on Wine.
Could you please run a regression test, to find out which change in Wine is responsible for that crash? Take a look here for more information how to do such a regression test: http://wiki.winehq.org/RegressionTesting
I'll try to find time for a regression test tomorrow! -- 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=39490 --- Comment #3 from Nikolay Sivov <bunglehead(a)gmail.com> --- Does notepad crash in clean prefix? -- 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=39490 --- Comment #4 from Sebastian Lackner <sebastian(a)fds-team.de> --- Just a wild guess, but it probably could be related to https://bugs.archlinux.org/task/46819. I get similar crashes with my distro build when I disable desktop integration and the Z:\ drive mapping. (However, for some unknown reason, they are not present with my own local build.) --- snip --- wine: Unhandled page fault on read access to 0x00000010 at address 0x7e64bdea (thread 0029), starting debugger... winedbg: Internal crash at 0xf70c9be1 --- snip --- -- 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=39490 --- Comment #5 from kolAflash <kolAflash(a)kolahilft.de> --- (In reply to Nikolay Sivov from comment #3)
Does notepad crash in clean prefix? No
(In reply to Sebastian Lackner from comment #1)
[...] Could you please run a regression test, to find out which change in Wine is responsible for that crash?
6f7dfe2cea4fdb9b61775023659193421c920278 is the first bad commit commit 6f7dfe2cea4fdb9b61775023659193421c920278 Author: Nikolay Sivov <nsivov(a)codeweavers.com> Date: Sun Oct 4 12:48:48 2015 +0300 gdi32: Implement GetFontFileInfo(). Signed-off-by: Nikolay Sivov <nsivov(a)codeweavers.com> :040000 040000 ad96260a965b1b1ad63f63ef861fc1150dbf67c7 a6aa54b4ed84424b898a12b0cd38b878290714da M dlls -- 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=39490 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |6f7dfe2cea4fdb9b61775023659 | |193421c920278 --- Comment #6 from Sebastian Lackner <sebastian(a)fds-team.de> --- There was indeed a mistake in that commit, which was fixed in: http://source.winehq.org/git/wine.git/commit/d774442e8 Does backporting this patch on top of 1.7.53 fix your 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=39490 Dmitry Timoshkov <dmitry(a)baikal.ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from Dmitry Timoshkov <dmitry(a)baikal.ru> --- Duplicate. *** This bug has been marked as a duplicate of bug 39488 *** -- 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=39490 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Wine 1.7.53 crashes when |Multiple programs crash on |starting (Wine 1.7.52 works |startup with Wine 1.7.53 |fine) |(heap corruption in gdi32 | |when Z: drive mapping is | |deleted) -- 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=39490 --- Comment #8 from kolAflash <kolAflash(a)kolahilft.de> --- (In reply to Sebastian Lackner from comment #6)
There was indeed a mistake in that commit, which was fixed in: http://source.winehq.org/git/wine.git/commit/d774442e8
Does backporting this patch on top of 1.7.53 fix your issue?
Just tested commit d774442e8 and the commit before it. Looks like d774442e8 fixes the problem! Alternatively adding a drive Z: to / also fixes it. Thanks for the help! -- 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=39490 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #9 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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)
-
wine-bugs＠winehq.org