https://bugs.winehq.org/show_bug.cgi?id=49013
Bug ID: 49013 Summary: League of Legends: Exception code c0000005 Product: Wine Version: 5.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: harry+winehq@unheit.net Distribution: ---
Created attachment 66992 --> https://bugs.winehq.org/attachment.cgi?id=66992 Logs for PID with WINEDEBUG=+seh,+pid,+tid,+loaddll,+kernelbase,+relay
When starting the Riot Launcher for League of Legends I often, but not always, get Unhandled exception code c0000005.
Attached is a log file with WINEDEBUG=+seh,+pid,+tid,+loaddll,+kernelbase,+relay. The log only contains entries for the PID that raises the exception.
I've tried to log even more, but then the exception does not occur. It seems timing sensitive. If other debug channels are required, I can try to enable them, but I don't know which ones are useful.
https://bugs.winehq.org/show_bug.cgi?id=49013
--- Comment #1 from harry harry+winehq@unheit.net --- Forgot to say, that I use wine-staging. I don't know if the bug only occurs in staging, because I can't run LoL with master.
If I set WINEDEBUG=fixme-all,warn+heap, the exception does not occur anymore. So there's at least a work-around.
https://bugs.winehq.org/show_bug.cgi?id=49013
Matías Zúñiga matias.nicolas.zc@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |matias.nicolas.zc@gmail.com
--- Comment #2 from Matías Zúñiga matias.nicolas.zc@gmail.com --- Created attachment 67068 --> https://bugs.winehq.org/attachment.cgi?id=67068 RtlpWaitForCriticalSection error
Until now i was using the LeagueClient, last week i tried to use the new RiotClient but i couldn't get it to work.
Most of the time i got a "RtlpWaitForCriticalSection" error, but yesterday i got the c0000005 exception code, so i found this report.
Using your workaround, i can finally get the new RiotClient to work!. Attached is the log what shows the RtlpWaitForCriticalSection i got most of the time.
https://bugs.winehq.org/show_bug.cgi?id=49013
--- Comment #3 from Matías Zúñiga matias.nicolas.zc@gmail.com --- Created attachment 67069 --> https://bugs.winehq.org/attachment.cgi?id=67069 HEAP_ValidateInUseArena error
Using you workaround, a number of errors are now visible after the "riot__rclient__event" event, where previously the error/exception occurred.
They can be identified looking for the "err:heap:HEAP_ValidateInUseArena" string e.g. "00b3:err:heap:HEAP_ValidateInUseArena Heap 0x110000: block 0xffe018 tail overwritten at 0xffe06c (byte 0/12 == 0x00)". That is probably the root cause, and printing the error avoids some weird timing issue
https://bugs.winehq.org/show_bug.cgi?id=49013
Michael McGuire spoon0042@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |spoon0042@hotmail.com
--- Comment #4 from Michael McGuire spoon0042@hotmail.com --- Also seeing this with Royal Quest with 5.8 staging. Similar anyway and the workaround gets it to start. Full output:
002c:fixme:winediag:start_process Wine Staging 5.8 is a testing version containing experimental patches. 002c:fixme:winediag:start_process Please mention your exact version when filing bug reports on winehq.org. 0024:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub 0024:err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0x7bc8d892
https://bugs.winehq.org/show_bug.cgi?id=49013
--- Comment #5 from Michael McGuire spoon0042@hotmail.com --- Oddly a local 32-bit build works. Also it could be one of the other bugs like this, some of them have been regression tested so I can try that in a bit.
-
WineHQ Bugzilla