https://bugs.winehq.org/show_bug.cgi?id=39019
Bug ID: 39019 Summary: Skyforge: Crash when accessing settings tab. Product: Wine Version: 1.7.48 Hardware: x86 OS: Mac OS X Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: philippe.groarke@gmail.com
Created attachment 51974 --> https://bugs.winehq.org/attachment.cgi?id=51974 Exception log.
I have debugged this as far as my knowledge can take me. Unfortunately there is no backtrace, as the game intercepts the crash with its own crash reporter. I have been digging and here is everything I have found. If you know of a way to get a backtrace when apps have crash reporters please share.
Note: The game runs extremely well, which is impressive.
Instructions: Install the game, run, access the settings tab, crash.
wine SkyforgeLoader_en.exe wine ~/.wine-skyforge/drive_c/users/youruser/Local Settings/Application Data/MyComGames/MyComGames.exe
Excpetion: 0022:trace:seh:raise_exception code=c0000005 flags=0 addr=0x97c5818c ip=97c5818c tid=0022 0022:trace:seh:raise_exception info[0]=00000001 0022:trace:seh:raise_exception info[1]=b06ec000 0022:trace:seh:raise_exception eax=b08d0810 ebx=0000008f ecx=00000000 edx=ffffffc0 esi=b08d1010 edi=b06ec030 0022:trace:seh:raise_exception ebp=0033e698 esp=0033e690 cs=001b ds=0023 es=0023 fs=1007 gs=000f flags=00210286 0022:trace:seh:call_stack_handlers calling handler at 0x155a739 code=c0000005 flags=0 0022:Call msvcr100._except_handler4_common(01f0b580,0155a3b4,0033e638,0033fec0,0033e36c,0033dcc8) ret=0155a759 0022:trace:seh:_except_handler4_common exception c0000005 flags=0 at 0x97c5818c handler=0x155a739 0x33e36c 0x33dcc8 cookie=b1a5f0a9 scope table=0x1c6bc58 cookies=-2/0,-124/0 0022:trace:seh:_except_handler4_common level 0 prev -2 filter 0x155a2a0 0022:Call msvcr100._XcptFilter(c0000005,0033db90) ret=0155a2b1 0022:trace:seh:_XcptFilter (c0000005,0x33db90)
Might be raised by? 0022:Call wined3d.wined3d_texture_create(10060048,0033e5d0,00000002,00000001,00000000,1882fc18,41eb259c,1882fc28) ret=41ea4fe1
I have found this interesting message in the logs, may not be related: 0060:Call msvcr100.wcsncpy_s(1b75ca00,000000a2,1e6ed078 L"<p align="center"><font size="14" color="#ffa040" letterSpacing="0.000000" kerning="1">Warning! Selected settings exceed your hardware specifications.</font></p>",000000a1) ret=0135795a
Errors in normal output, most likely unrelated/not harmful: err:dbghelp_stabs:stabs_parse Unknown stab type 0x0a [0802/093516:ERROR:network_change_notifier_win.cc(158)] WSALookupServiceBegin failed with: 8 [0802/093517:ERROR:renderer_main.cc(212)] Running without renderer sandbox err:avicap:query_video_device Video 4 Linux support not enabled
https://bugs.winehq.org/show_bug.cgi?id=39019
philippe.groarke@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |http://sf.my.com/
https://bugs.winehq.org/show_bug.cgi?id=39019
--- Comment #1 from philippe.groarke@gmail.com --- Quick update. This may be a duplicate of bug 34480. I am still trying to get a backtrace using different debugging methods, but so far no luck. I have attached a new and improved log.
https://bugs.winehq.org/show_bug.cgi?id=39019
--- Comment #2 from philippe.groarke@gmail.com --- Created attachment 51985 --> https://bugs.winehq.org/attachment.cgi?id=51985 Better log
https://bugs.winehq.org/show_bug.cgi?id=39019
--- Comment #3 from philippe.groarke@gmail.com --- So indeed, this is a duplicate of the mipmap memory bug.
Editing wined3d/resource.c, wined3d_resource_allocate_sysmem like so: if (!(mem = HeapAlloc(GetProcessHeap(), HEAP_ZERO_MEMORY, resource->size * 2 + 15))) temporarily "fixes" the crash.
I will still provide what resembles like the correct backtraces for the crash. I ended up using a neat dtrace command to log the backtraces.
I have attached the full log: sudo dtrace -n 'proc:::signal-handle /pid == $target/ { ustack(); }' -p <process ID>
And a filtered log (which ignores SIGUSR1): sudo dtrace -n 'proc:::signal-handle /pid == $target && args[0] != SIGUSR1/ { printf("signal %d\n", args[0]); ustack(); }' -p <process ID>
Of interest:
0 1177 sendsig:signal-handle signal 11
libsystem_platform.dylib`_platform_memmove$VARIANT$sse42+0x9c msvcr100.dll.so`MSVCRT_memcpy+0x26 wine`__wine_dos+0x1282c24
https://bugs.winehq.org/show_bug.cgi?id=39019
--- Comment #4 from philippe.groarke@gmail.com --- Created attachment 51987 --> https://bugs.winehq.org/attachment.cgi?id=51987 dtrace unfiltered
https://bugs.winehq.org/show_bug.cgi?id=39019
--- Comment #5 from philippe.groarke@gmail.com --- Created attachment 51988 --> https://bugs.winehq.org/attachment.cgi?id=51988 dtrace with SIGUSR1 filtered out
https://bugs.winehq.org/show_bug.cgi?id=39019
philippe.groarke@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE
--- Comment #6 from philippe.groarke@gmail.com --- Duplicate confirmed
*** This bug has been marked as a duplicate of bug 34480 ***
https://bugs.winehq.org/show_bug.cgi?id=39019
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org