[Bug 33974] New: The Last Remnant crashes frequently
http://bugs.winehq.org/show_bug.cgi?id=33974 Bug #: 33974 Summary: The Last Remnant crashes frequently Product: Wine Version: 1.6-rc4 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: michael.blumenkrantz(a)gmail.com Classification: Unclassified When playing TLR, the game is guaranteed to crash at certain points; one such example is when entering the Sacred Lands in the game. Additionally, the game crashes repeatedly during fights when displaying certain enemy attacks from certain angles; these crashes do not leave any useful info that I have been able to find, though I am willing to provide any logs on demand. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #1 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> 2013-07-07 08:33:56 CDT --- A game save just before a fight which triggers one such crash can be found here: http://dev.enlightenment.fr/~discomfitor/savegame00 To trigger the crash with this save, simply walk forward, sit through or skip the brief cinematic, then continue through the boss fight until the crash occurs. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 Dan Kegel <dank(a)kegel.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download URL| |http://www.lastremnant-game | |.com/ CC| |dank(a)kegel.com --- Comment #2 from Dan Kegel <dank(a)kegel.com> 2013-07-07 12:38:29 CDT --- Thanks for the game save. Can you also attach a log? http://wiki.winehq.org/FAQ#get_log -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #3 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> 2013-07-07 13:21:42 CDT --- Created attachment 45147 --> http://bugs.winehq.org/attachment.cgi?id=45147 crash log output from crash using attached game save -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #4 from Dan Kegel <dank(a)kegel.com> 2013-07-07 13:26:35 CDT --- I don't see a backtrace in there. Maybe try again after winetricks nocrashdialog ? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #5 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> 2013-07-07 13:32:28 CDT --- (In reply to comment #4)
I don't see a backtrace in there. Maybe try again after winetricks nocrashdialog ?
You are correct; there is no backtrace, nor does wine seem to know that it has crashed. I do get a 1.3gb core dump each time, however, and it is definitely crashing with SIGSEGV. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #6 from Dan Kegel <dank(a)kegel.com> 2013-07-07 15:05:43 CDT --- I bet steam's crashhandler.dll or friends is catching them. +seh can add a little info to the log about the crash, but probably isn't useful in and of itself. (I wonder what happens if you disable crashhandler.dll.) -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 Qian Hong <fracting(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fracting(a)gmail.com --- Comment #7 from Qian Hong <fracting(a)gmail.com> 2013-07-07 15:10:24 CDT --- (In reply to comment #5)
(In reply to comment #4) I do get a 1.3gb core dump each time, however, and it is definitely crashing with SIGSEGV.
Hi, If you use winedbg to open the core dump, could you get a backtrace? $ winedbg xxx.dmp or somthing like that -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #8 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> 2013-07-08 00:00:33 CDT --- (In reply to comment #6)
I bet steam's crashhandler.dll or friends is catching them.
+seh can add a little info to the log about the crash, but probably isn't useful in and of itself.
(I wonder what happens if you disable crashhandler.dll.)
I'll test this and report back after work today. (In reply to comment #7)
(In reply to comment #5)
(In reply to comment #4) I do get a 1.3gb core dump each time, however, and it is definitely crashing with SIGSEGV.
Hi,
If you use winedbg to open the core dump, could you get a backtrace?
$ winedbg xxx.dmp or somthing like that
Unfortunately the cores are truncated (despite having set them to unlimited size with ulimit). Loading them reveals a three frame stack with no symbols. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #9 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> 2013-07-08 09:28:58 CDT --- (In reply to comment #6)
I bet steam's crashhandler.dll or friends is catching them.
+seh can add a little info to the log about the crash, but probably isn't useful in and of itself.
(I wonder what happens if you disable crashhandler.dll.)
Okay, I tried disabling crashhandler: no change. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #10 from Qian Hong <fracting(a)gmail.com> 2013-07-08 09:37:40 CDT --- (In reply to comment #8)
$ winedbg xxx.dmp or somthing like that
Unfortunately the cores are truncated (despite having set them to unlimited size with ulimit). Loading them reveals a three frame stack with no symbols.
Did you installed debug symbol for Wine? I remember the Ubuntu wine-dbg package was broken some time ago, not sure how is the current states, but it would be great if you can try build Wine your self and reproduce the crashing, then read the mini dump file with winedbg to see if there is any symbols. Even without symbols, could you paste the frame stack then? Thanks a lot! -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #11 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> 2013-07-08 09:41:10 CDT --- (In reply to comment #10)
(In reply to comment #8)
$ winedbg xxx.dmp or somthing like that
Unfortunately the cores are truncated (despite having set them to unlimited size with ulimit). Loading them reveals a three frame stack with no symbols.
Did you installed debug symbol for Wine? I remember the Ubuntu wine-dbg package was broken some time ago, not sure how is the current states, but it would be great if you can try build Wine your self and reproduce the crashing, then read the mini dump file with winedbg to see if there is any symbols.
Even without symbols, could you paste the frame stack then?
Thanks a lot!
I have debug symbols available, but the frame stack from the core dumps is completely blank. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #12 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> 2013-07-08 10:31:20 CDT --- Created attachment 45161 --> http://bugs.winehq.org/attachment.cgi?id=45161 second crash output I just tested with wine sound disabled, and I was able to get past the battle sequence in the save (though it crashed immediately after). Setting to pulseaudio has the same result, so I'm thinking this particular crash is somehow a wine alsa driver bug? Output from the next crash is attached, frame stack from backtrace of that crash also contains no usable symbols. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #13 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> --- This is still an issue with 1.7.20, and I'm regretting not buying a couple steam keys last time it was on sale to give away to developers :/ -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #14 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> --- Created attachment 48820 --> http://bugs.winehq.org/attachment.cgi?id=48820 +seh,+tid log -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 Sebastian Lackner <sebastian(a)fds-team.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian(a)fds-team.de -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #15 from Sebastian Lackner <sebastian(a)fds-team.de> --- Hi, The problem could be related to exception handling, but unfortunately I didn't see anything obvious wrong. Its a bit weird that the exception is repeated over and over again, but this could also just be bad programming, and doesn't necessarily mean an error. Moreover the log stil doesn't contain a good reason why the program crashes. Could you also attach a log with +pid,+relay,+seh please? When the file is too big just compress it before attaching to this bug report, or store it at an external location. Regards, Sebastian -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #16 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> --- (In reply to Sebastian Lackner from comment #15)
Hi,
The problem could be related to exception handling, but unfortunately I didn't see anything obvious wrong. Its a bit weird that the exception is repeated over and over again, but this could also just be bad programming, and doesn't necessarily mean an error. Moreover the log stil doesn't contain a good reason why the program crashes.
Could you also attach a log with +pid,+relay,+seh please? When the file is too big just compress it before attaching to this bug report, or store it at an external location.
Regards, Sebastian
I've created a log as requested, which can be found here (~51MB): http://devs.enlightenment.org/~discomfitor/tlr.log.xz This was made with RelayExclude="ntdll.RtlEnterCriticalSection;ntdll.RtlLeaveCriticalSection;kernel32.48;kernel32.49;kernel32.94;kernel32.95;kernel32.96;kernel32.97;kernel32.98;KERNEL32.GetLastError;KERNEL32.SetLastError;KERNEL32.FlsGetValue;KERNEL32.SetLastError;KERNEL32.GetLastError;KERNEL32.TlsGetValue;ntdll.RtlAllocateHeap;ntdll.RtlSizeHeap;ntdll.RtlFreeHeap;ntdll.RtlTryEnterCriticalSection;wined3d.wined3d_mutex_unlock;wined3d.wined3d_mutex_lock;KERNEL32.WaitForSingleObject;ntdll.NtQueryAttributesFile;winsock.WS2_recv_base;winsock.wsaErrno;winhttp:get_system_proxy_autoconfig_url;ntdll.FILE_CreateFile;ntdll.NtResetEvent;ntdll.NtWaitForMultipleObjects;KERNEL32.SetEvent;ntdll.NtSetEvent;ws2_32.select;ws2_32.__WSAFDIsSet;ntdll.wine_server_release_fd;ntdll.wine_server_handle_to_fd;ws2_32.WSAGetLastError;ws2_32.accept;KERNEL32.QueryPerformanceCounter;ntdll.NtQueryPerformanceCounter;KERNEL32.ResetEvent;KERNEL32.WaitForMultipleObjects;ntdll.RtlReAllocateHeap;msvcr80.memcpy;ntdll.NtDelayExecution;KERNEL32.Sleep;msvcr80.memset;ntdll.RtlDosPathNameToNtPathName_U;wined3d.wined3d_device_set_vs_consts_f;wined3d.wined3d_device_set_ps_consts_f;opengl32.wglGetCurrentContext;KERNEL32.InterlockedCompareExchange;ntdll.RtlFreeUnicodeString;ntdll.RtlAcquireResourceShared;ntdll.RtlReleaseResource;wined3d.wined3d_device_set_sampler_state;msvcr80._CIpow;ntdll.RtlNtStatusToDosError;KERNEL32.GetTickCount;msvcr80.wcsncpy;KERNEL32.ReadFile;ntdll.NtReadFile;wined3d.wined3d_device_set_texture;user32.ShowWindow;msvcr80.wcsstr;wined3d.wined3d_device_set_render_state;msvcr80._aligned_free;msvcr80._aligned_malloc;msvcr80._wcsnicmp;msvcr80._wcsicmp;msvcr80.memmove" Note that the decompressed filesize is around 8GB, and it took me a little over 1 hour to compress, so this will require a lot of time and space to decompress for viewing. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #17 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> --- Probably worth noting that this game is now 75% discounted for the Steam Summer Sale. If any wine developers are interested in looking into this, I will gift you a copy of the game. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #18 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> --- I've just encountered a different type of crash which occurs when I try to enter a certain area in the game. A log can be found here, created the same way as the previous one: http://devs.enlightenment.org/~discomfitor/tlr2.log.xz -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net --- Comment #19 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, the exceptions are harmless and expected. --- snip --- ... 004d:Call shell32.SHGetKnownFolderPath(7eff7f50,00008000,00000000,7efff70c) ret=7eff18e3 ... 004d:Call KERNEL32.GetSystemDirectoryW(0033e168,00000104) ret=7e383250 004d:Ret KERNEL32.GetSystemDirectoryW() retval=00000013 ret=7e383250 004d:Call advapi32.RegQueryValueExW(0000005c,7e3cb220 L"ProfilesDirectory",00000000,0033dcd8,0033df60,0033dcdc) ret=7e382ac0 004d:Ret advapi32.RegQueryValueExW() retval=00000000 ret=7e382ac0 004d:Call advapi32.GetUserNameW(0033e168,0033dd54) ret=7e382fda 004d:Ret advapi32.GetUserNameW() retval=00000001 ret=7e382fda 004d:Call shlwapi.PathAppendW(0033e7e8 L"C:\\users",0033e168 L"root") ret=7e382fef 004d:Ret shlwapi.PathAppendW() retval=00000001 ret=7e382fef 004d:Call shlwapi.PathAppendW(0033e7e8 L"C:\\users\\root",0033dd72 L"\\Desktop") ret=7e38301e 004d:Ret shlwapi.PathAppendW() retval=00000001 ret=7e38301e ... --- snip --- You are running Wine as root. NEVER do this! Any bug reports/logs resulting from that are automatically invalid. You need to reinstall _everything_ in a clean WINEPREFIX owned by a normal user. Regards -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #20 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> --- (In reply to Anastasius Focht from comment #19)
Hello folks,
the exceptions are harmless and expected.
--- snip --- ... 004d:Call shell32.SHGetKnownFolderPath(7eff7f50,00008000,00000000,7efff70c) ret=7eff18e3 ... 004d:Call KERNEL32.GetSystemDirectoryW(0033e168,00000104) ret=7e383250 004d:Ret KERNEL32.GetSystemDirectoryW() retval=00000013 ret=7e383250 004d:Call advapi32.RegQueryValueExW(0000005c,7e3cb220 L"ProfilesDirectory",00000000,0033dcd8,0033df60,0033dcdc) ret=7e382ac0 004d:Ret advapi32.RegQueryValueExW() retval=00000000 ret=7e382ac0 004d:Call advapi32.GetUserNameW(0033e168,0033dd54) ret=7e382fda 004d:Ret advapi32.GetUserNameW() retval=00000001 ret=7e382fda 004d:Call shlwapi.PathAppendW(0033e7e8 L"C:\\users",0033e168 L"root") ret=7e382fef 004d:Ret shlwapi.PathAppendW() retval=00000001 ret=7e382fef 004d:Call shlwapi.PathAppendW(0033e7e8 L"C:\\users\\root",0033dd72 L"\\Desktop") ret=7e38301e 004d:Ret shlwapi.PathAppendW() retval=00000001 ret=7e38301e ... --- snip ---
You are running Wine as root. NEVER do this! Any bug reports/logs resulting from that are automatically invalid.
You need to reinstall _everything_ in a clean WINEPREFIX owned by a normal user.
Regards
Done, and there is no change at all in the status of the crashes that I reported in comment #16. I did discover, however, that when using a 32bit wine prefix, some of the other crashes, eg. comment #18, disappear. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #21 from Anastasius Focht <focht(a)gmx.net> --- Hello Mike, I installed that game and loaded the attached savegame. Proceeded with the fight against that boss/guy but I don't get any crash. Regards -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #22 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> --- (In reply to Anastasius Focht from comment #21)
Hello Mike,
I installed that game and loaded the attached savegame. Proceeded with the fight against that boss/guy but I don't get any crash.
Regards
That's very interesting. Did the boss guy kill one of your group leaders, leading to "botch" status? This triggers a crash 100% of the time for me. I just tested the save again here and it crashes when this 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #23 from Anastasius Focht <focht(a)gmx.net> --- Hello Mike, --- quote --- That's very interesting. Did the boss guy kill one of your group leaders, leading to "botch" status? This triggers a crash 100% of the time for me. --- quote --- Yes, I've had at least two group leaders killed and it showed 'botched' for each (remaining members do not take commands anymore). And I lost the battle in the end :| Regards -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #24 from Sebastian Lackner <sebastian(a)fds-team.de> --- I assume that Anastasius is testing with the latest uptstream version (>1.7.20) - maybe it was fixed as a side effect just within the last couple of commits? *hope* ;) -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- URL|http://www.lastremnant-game |http://store.steampowered.c |.com/ |om/app/23310/ Summary|The Last Remnant crashes |The Last Remnant (Steam) |frequently |crashes frequently --- Comment #25 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, I reverted to Wine 1.7.20 and it still works - even in 'botched' scenarios. Can you run the game in mid-res 'windowed' mode, e.g. 960x720 and the like. Regards -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 --- Comment #26 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> --- (In reply to Anastasius Focht from comment #25)
Hello folks,
I reverted to Wine 1.7.20 and it still works - even in 'botched' scenarios. Can you run the game in mid-res 'windowed' mode, e.g. 960x720 and the like.
Regards
I've just tested this with a couple other resolutions, and I still get a crash. I wonder if this is somehow a driver bug? I'm using nvidia binary. Also possibly noteworthy is that I'm not using pulseaudio here, so it's just using alsa. I tried disabling sound with 'winetricks sound=disabled', but this seems to have no effect on the game, and sound continues to play. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #27 from Mike Blumenkrantz <michael.blumenkrantz(a)gmail.com> --- This turned out to be an nvidia (binary) driver bug. Everything appears to work fine now. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=33974 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #28 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.
https://bugs.winehq.org/show_bug.cgi?id=33974 Bruno Jesus <00cpxxx(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |UPSTREAM -- 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