[Bug 42584] New: League of Legends: LeagueClient.exe hangs at startup logo
https://bugs.winehq.org/show_bug.cgi?id=42584 Bug ID: 42584 Summary: League of Legends: LeagueClient.exe hangs at startup logo Product: Wine Version: 2.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: hevanen(a)googlemail.com Distribution: --- Created attachment 57504 --> https://bugs.winehq.org/attachment.cgi?id=57504 Full console output When launching LeagueClient.exe, the application often hangs at the "League of Legends" logo. This happens about 2 out of 3 times on average, but sometimes it takes up to 10 attempts to get it to run. The terminal shows an endless repeat of errors like the following: err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c: HEAP.critSection" wait timed out in thread 005c, blocked by 007e, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c: HEAP.critSection" wait timed out in thread 0051, blocked by 007e, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c: HEAP.critSection" wait timed out in thread 008d, blocked by 007e, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c: HEAP.critSection" wait timed out in thread 0052, blocked by 007e, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c: HEAP.critSection" wait timed out in thread 0060, blocked by 007e, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x7bcebaa0 "loader.c: loader_section" wait timed out in thread 007d, blocked by 007c, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c: HEAP.critSection" wait timed out in thread 007c, blocked by 007e, retrying (60 sec) err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c: HEAP.critSection" wait timed out in thread 0063, blocked by 007e, retrying (60 sec) -- 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=42584 João Vitor Verona Biazibetti <joaaoverona(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joaaoverona(a)gmail.com --- Comment #1 from João Vitor Verona Biazibetti <joaaoverona(a)gmail.com> --- Can confirm. This has been happening for a while, with a similar terminal output to what David K. posted. (Fedora 24, x86-64, Wine-staging 2.0) -- 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=42584 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #2 from winetest(a)luukku.com --- (In reply to João Vitor Verona Biazibetti from comment #1)
Can confirm. This has been happening for a while, with a similar terminal output to what David K. posted. (Fedora 24, x86-64, Wine-staging 2.0)
There is already wine-staging 2.7 version. Does overriding CSMT on and off change anything? -- 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=42584 --- Comment #3 from David K. <hevanen(a)googlemail.com> --- Still happens with 2.8-staging. Disabling CSMT does not change anything. -- 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=42584 Jactry Zeng <jactry92(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jactry92(a)gmail.com -- 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=42584 --- Comment #4 from winetest(a)luukku.com --- (In reply to David K. from comment #3)
Still happens with 2.8-staging. Disabling CSMT does not change anything.
I don't know if this helps at all but worth to try. Does WINEDEBUG-all, wine game.exe 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=42584 Kirurgs <edzis(a)inbox.lv> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |edzis(a)inbox.lv --- Comment #5 from Kirurgs <edzis(a)inbox.lv> --- Hi! I have tried quite a lot of wine versions, from 2.0-rc2 to 2.8 staging, all of them have the same problem as OP. But I have a nice situation where I can compare couple of systems :) I have one which actually works, that is Phenom II 975 BE + nVidia 1050 2GB (nvidia-375 driver) + Wine 2.0-staging, works w/o problems. Other is Ryzen 1700 + HD7850 1GB (mesa, latest from git - padoka) + Wine > 2.0, does not 95% of tries, there are very rare cases when it starts, but then clicking in pre-actual-game stuff, it crashes. Sometimes it spits out something like "err:seh:setup_exception_record stack overflow 832 bytes in thread 0087 eip f73dd8f0 esp 027e0ff0 stack 0x27e0000-0x27e1000-0x28e0000". Somehow I felt that forcing Ryzen to lowest freq possible gets me a little further but that may be misleading, as I still can not play the game. In common - they are both Ubuntu 16.04 up-to-date stuff. I'm open to do any type of debugging, patches, etc., since finally I have a decent computer where I can compile stuff fast. BR, Eduardo -- 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=42584 --- Comment #6 from Kirurgs <edzis(a)inbox.lv> --- Forgot to mention that WINEDEBUG=-all does not help a tiny bit, CSMT - the same, on / off does not change a thing. I preferred to play LOL 6.x using Gallium9 on radeonsi, for 7.x (which is the new shiny problematic version) switching it on and off does not help either. I have not tried AMDGPU thing tho, will that be beneficial? -- 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=42584 --- Comment #7 from Kirurgs <edzis(a)inbox.lv> --- The same issue with 2.9. -- 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=42584 --- Comment #8 from winetest(a)luukku.com --- (In reply to Kirurgs from comment #7)
The same issue with 2.9.
Have you tried reinstalling the game from stratch? I think it's not possible currently install without some workaround. -- 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=42584 --- Comment #9 from Kirurgs <edzis(a)inbox.lv> --- No, I have not, as I have fully functioning LOL installation. I did not mention previously, but I have copied installation from *working* computer (namely Phenom) to Ryzen system, but that did not get anything further. I have tried standard mesa, mesa-git and in addition to that I have tried all that on ArchLinux as well. Lately, I see more "err:seh:setup_exception_record stack overflow 832 bytes in thread 0087 eip f73dd8f0 esp 027e0ff0 stack 0x27e0000-0x27e1000-0x28e0000" type of errors right after game shows login screen and before animation appears. When I turn off CSMT and wine-nine, it's more likely that I get the "err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c: HEAP.critSection" wait timed out in thread 005c, blocked by 007e, retrying (60 sec)". -- 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=42584 --- Comment #10 from winetest(a)luukku.com --- (In reply to Kirurgs from comment #9)
No, I have not, as I have fully functioning LOL installation.
I did not mention previously, but I have copied installation from *working* computer (namely Phenom) to Ryzen system, but that did not get anything further.
I have tried standard mesa, mesa-git and in addition to that I have tried all that on ArchLinux as well.
Lately, I see more "err:seh:setup_exception_record stack overflow 832 bytes in thread 0087 eip f73dd8f0 esp 027e0ff0 stack 0x27e0000-0x27e1000-0x28e0000" type of errors right after game shows login screen and before animation appears. When I turn off CSMT and wine-nine, it's more likely that I get the "err:ntdll:RtlpWaitForCriticalSection section 0x870060 "heap.c: HEAP.critSection" wait timed out in thread 005c, blocked by 007e, retrying (60 sec)".
Did I understood correctly that you copied the game from windows install? Even you used Linux based system It's not enough just to copy the game itself, wine needs to setup certain registery keys for sure. -- 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=42584 --- Comment #11 from Kirurgs <edzis(a)inbox.lv> --- No, those are 2 rather old installations of LOL on Linux in wine. Both were upgraded +/- about the same time to "new client", because there was no option to continue playing "old client". One system works, other does not. It's all in comment #5: https://bugs.winehq.org/show_bug.cgi?id=42584#c5 . So I thought, I could just copy working installation over to other system where LOL didn't work in the hope that it might work, which did not help. So I ruled out "bad upgrade". -- 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=42584 --- Comment #12 from winetest(a)luukku.com --- (In reply to Kirurgs from comment #11)
No, those are 2 rather old installations of LOL on Linux in wine. Both were upgraded +/- about the same time to "new client", because there was no option to continue playing "old client". One system works, other does not. It's all in comment #5: https://bugs.winehq.org/show_bug.cgi?id=42584#c5 .
So I thought, I could just copy working installation over to other system where LOL didn't work in the hope that it might work, which did not help. So I ruled out "bad upgrade".
Ok then. But did you copy whole .wine directory or just the game directory? I just wonder if the game has broken someway with wine (wine upgrade or something similar). -- 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=42584 --- Comment #13 from Kirurgs <edzis(a)inbox.lv> --- I copied everything. On slower machine with faster nvidia it works, on faster machine with mesa and slower hd7850 does not. -- 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=42584 --- Comment #14 from Kirurgs <edzis(a)inbox.lv> --- Tried with 2.10-staging, does not work. -- 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=42584 --- Comment #15 from Kirurgs <edzis(a)inbox.lv> --- Maybe it had something to do with game updates or system updates, but now it works using wine 2.10. -- 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=42584 Michel Le Bihan <michel(a)lebihan.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |michel(a)lebihan.pl --- Comment #16 from Michel Le Bihan <michel(a)lebihan.pl> --- Created attachment 59082 --> https://bugs.winehq.org/attachment.cgi?id=59082 Errors in console -- 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=42584 --- Comment #17 from Michel Le Bihan <michel(a)lebihan.pl> --- Hello, I have the same issue, but the errors in my console are slightly different. I put them in an attachment. My Wine version is `wine-2.14 (Debian 2.14-1)` and my system is Debian Stretch with the 4.12.10-gnu kernel. My system is 64bit and I am using a 32bit prefix. I set the Windows version to XP. I managed to get the game 'working' (at least go to playing a match) with Wine 1.9.2-staging-lol-i386. It is the version used in Lutris (https://lutris.net/games/install/3552/view). Since it works with a previous version, that issue should be a regression. -- 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=42584 joaopa <jeremielapuree(a)yahoo.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree(a)yahoo.fr --- Comment #18 from joaopa <jeremielapuree(a)yahoo.fr> --- Does the bug still occur with wine-7.0-rc5? -- 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=42584 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Abandoned? CC| |o.dierick(a)piezo-forte.be --- Comment #19 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Current League of Legends client hangs on the startup logo for other reasons (bug 54793). I think we should abandon this bug. 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla