[Bug 43713] New: regression: Skyrim instantly crashes when a key is pressed as of wine 2.17
https://bugs.winehq.org/show_bug.cgi?id=43713 Bug ID: 43713 Summary: regression: Skyrim instantly crashes when a key is pressed as of wine 2.17 Product: Wine Version: 2.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: alexchandel(a)gmail.com Distribution: --- As of wine 2.17, Skyrim now immediately crashes as soon as a key is pressed in game. Replication steps: 1. Launch Skyrim 2. Click "Continue" from main menu 3. Wait for game to load... 4. Press the "w" key 5. Skyrim crashes. The lone error message: ... fixme:xinput:XInputSetState (index 0, vibration 0x3abaf630) Stub! fixme:xinput:XInputSetState (index 0, vibration 0x37f8f630) Stub! fixme:xinput:XInputSetState (index 0, vibration 0x3abaf630) Stub! err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0xa15ba20f -- 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=43713 --- Comment #1 from Rosanne DiMesio <dimesio(a)earthlink.net> --- I can't reproduce this; Skyrim works fine on my system in 2.17. Please run a regression test. https://wiki.winehq.org/Regression_Testing -- 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=43713 alexchandel(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- OS|Linux |Mac OS X --- Comment #2 from alexchandel(a)gmail.com --- My system is macOS 10.12.5, with wine set to Windows XP (due to bug 42674). It happens after loading any Skyrim state. -- 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=43713 --- Comment #3 from alexchandel(a)gmail.com --- It also happens with wine set to Windows 7, with the effects of bug 42674. -- 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=43713 Ken Thomases <ken(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ken(a)codeweavers.com --- Comment #4 from Ken Thomases <ken(a)codeweavers.com> --- Does Wine show a crash dialog? If so, save the backtrace from there and attach it to the bug. What version of Wine were you using when Skyrim last worked? And, of course, try to perform the regression test that Rosanne suggested. -- 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=43713 --- Comment #5 from alexchandel(a)gmail.com --- (In reply to Ken Thomases from comment #4)
Does Wine show a crash dialog? If so, save the backtrace from there and attach it to the bug.
What version of Wine were you using when Skyrim last worked? And, of course, try to perform the regression test that Rosanne suggested.
No crash dialog or backtrace. The only sign it's crashed, other than the game window disappearing, is the wine output "err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0xa15ba20f". Are there any WINEDEBUG options that would reveal more information on the crash? The last version it worked on was 2.16, so the regression is very recent. -- 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=43713 --- Comment #6 from alexchandel(a)gmail.com --- (In reply to Ken Thomases from comment #4)
Does Wine show a crash dialog? If so, save the backtrace from there and attach it to the bug.
What version of Wine were you using when Skyrim last worked? And, of course, try to perform the regression test that Rosanne suggested.
This might be related to bug 43784 -- 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=43713 --- Comment #7 from alexchandel(a)gmail.com --- (In reply to Rosanne DiMesio from comment #1)
I can't reproduce this; Skyrim works fine on my system in 2.17.
Please run a regression test. https://wiki.winehq.org/Regression_Testing
I don't have a machine to run the test on at the moment, but I may in the future. Do you want me to run Skyrim with any WINEDEBUG options to pinpoint the error? (In reply to Ken Thomases from comment #4)
Does Wine show a crash dialog? If so, save the backtrace from there and attach it to the bug.
What version of Wine were you using when Skyrim last worked? And, of course, try to perform the regression test that Rosanne suggested.
Do you want me to run Skyrim with any WINEDEBUG options? -- 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=43713 --- Comment #8 from Ken Thomases <ken(a)codeweavers.com> --- Created attachment 59322 --> https://bugs.winehq.org/attachment.cgi?id=59322 Patch to ignore access violations to get a macOS crash report The best thing would be to do that regression test. As for logging channels, it's hard to know what useful ones would be with so few details. A +tid,+relay,+seh log may be informative, but it will be huge and full of unrelated noise and thus hard to analyze. Another possible approach is to build with the attached patch applied. It will make it so that neither Wine nor Skyrim can catch the crash. Instead, macOS will catch it and generate its own crash report. That crash report may be informative. On the other hand, the patch may break things so that Steam or Skyrim no longer even get to the point of the crash we're trying to diagnose. If that happens, then back it out. -- 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=43713 --- Comment #9 from alexchandel(a)gmail.com --- (In reply to Ken Thomases from comment #8)
Created attachment 59322 [details] Patch to ignore access violations to get a macOS crash report
The best thing would be to do that regression test.
As for logging channels, it's hard to know what useful ones would be with so few details. A +tid,+relay,+seh log may be informative, but it will be huge and full of unrelated noise and thus hard to analyze.
Another possible approach is to build with the attached patch applied. It will make it so that neither Wine nor Skyrim can catch the crash. Instead, macOS will catch it and generate its own crash report. That crash report may be informative. On the other hand, the patch may break things so that Steam or Skyrim no longer even get to the point of the crash we're trying to diagnose. If that happens, then back it out.
The mystery deepens: the crash doesn't occur with the wine-staging 2.17 I built, only the normal wine 2.17 I built. And it occurs consistently, between builds. Is there any way to activate the +tid,+relay,+seh during the life of a process (e.g. during the TESV.exe loading, just before the crash occurs)? -- 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=43713 Vlad <vblanton(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vblanton(a)gmail.com --- Comment #10 from Vlad <vblanton(a)gmail.com> --- It's been a couple years. @alexchandel did this regression still occur with later versions of 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla