[Bug 49025] New: League of Legends crashes at game start (wine 5.7 regression)
https://bugs.winehq.org/show_bug.cgi?id=49025 Bug ID: 49025 Summary: League of Legends crashes at game start (wine 5.7 regression) Product: Wine Version: 5.7 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: aguertin+wine(a)aguertin.net Distribution: --- League of Legends crashes at game start using wine-staging 5.7. It works fine using wine-staging 5.6 (plus some league-specific patches). I will bisect. Gentoo, x86_64. -- 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=49025 aguertin+wine(a)aguertin.net changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |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=49025 juliansperling(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |juliansperling(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=49025 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be --- Comment #1 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, Probably duplicate of 49011. You should wait until that bug is fixed before wasting efforts to bisect. 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.
https://bugs.winehq.org/show_bug.cgi?id=49025 --- Comment #2 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- *link: bug 49011 -- 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=49025 --- Comment #3 from aguertin+wine(a)aguertin.net --- Thanks but this seems to be a different bug. I've narrowed the regression range to: wine e3cf3823f89 / staging e2c24478: works wine a55feef63a7 / staging a23c0760: crashes Within that range are two patchsets being moved from wine-staging to wine, and one unrelated wine change. -- 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=49025 aguertin+wine(a)aguertin.net changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |fd7992972b252ed262d33ef604e | |9e1235d2108c5 --- Comment #4 from aguertin+wine(a)aguertin.net --- All right, looks like this is a regression from commit fd799297 from bug 48817. See also: Bug 48961 (same regression sha1, different cause, fixed in 5.7) Bug 48971 (same regression sha1, different cause, fixed in 5.7) Bug 49007 (same regression sha1, still open as of 5.7) -- 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=49025 gort818(a)gmail.com <gort818(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gort818(a)gmail.com --- Comment #5 from gort818(a)gmail.com <gort818(a)gmail.com> --- This is the same commit fd799297 that caused issues with Star Citizen 49007 -- 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=49025 Andrew Wesie <awesie(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |awesie(a)gmail.com --- Comment #6 from Andrew Wesie <awesie(a)gmail.com> --- The patch in bug 49007 to revert the offending commit fixes loading the League of Legends client for me. I'm guessing this bug should be marked as either confirmed or dupe. -- 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=49025 --- Comment #7 from Andrew Wesie <awesie(a)gmail.com> --- (In reply to Andrew Wesie from comment #6)
The patch in bug 49007 to revert the offending commit fixes loading the League of Legends client for me. I'm guessing this bug should be marked as either confirmed or dupe.
After further testing, the behavior I'm observing is closer to bug 49013 so my observation is likely to be unproductive. Apologies. -- 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=49025 --- Comment #8 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- Hello, This bug has no terminal output and bug 49013 has no regression test result. If both bugs are the same we could mark the less detailed bug duplicate. @OP: Was your original issue 'Unhandled exception code c0000005', like bug 49013? 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.
https://bugs.winehq.org/show_bug.cgi?id=49025 --- Comment #9 from aguertin+wine(a)aguertin.net --- (In reply to Olivier F. R. Dierick from comment #8)
@OP: Was your original issue 'Unhandled exception code c0000005', like bug 49013?
This is not the same as bug 49013. There is no terminal output from the issue I am seeing. There is a dialog created by the league of legends crash handler process that says "A critical error has been detected and the process must be terminated." and has options for creating a crash dump to share with Riot. (Willing to share that here, if it would be helpful.) This may be the same as bug 49007, but there's not enough info to be sure. Reverting fd79929 fixes both of them, but bug 48961 and bug 48971 were both fixed without reverting, and they were separate bugs that needed separate fixes. -- 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=49025 Manuel <mail+wine(a)m-reimer.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mail+wine(a)m-reimer.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.
https://bugs.winehq.org/show_bug.cgi?id=49025 chronobserver(a)disroot.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chronobserver(a)disroot.org --- Comment #10 from chronobserver(a)disroot.org --- I'm running wine-lol 5.5-2 installed via Lutris and the game is crashing with the same error for me. -- 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=49025 Simon the Sorcerer <sur3(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sur3(a)gmx.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.
https://bugs.winehq.org/show_bug.cgi?id=49025 aguertin+wine(a)aguertin.net changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1|fd7992972b252ed262d33ef604e |a55feef63a751a04b9f19011d23 |9e1235d2108c5 |2f3456502d655 --- Comment #11 from aguertin+wine(a)aguertin.net --- Putting in more work for this, I've found that it's not fd79929 that caused the regression, but rather a55feef6 (two commits later) commit a55feef63a751a04b9f19011d232f3456502d655 Author: Alexandre Julliard <julliard(a)winehq.org> Date: Tue Apr 14 21:58:56 2020 +0200 ntdll: Always use the loaded path as builtin module file name. If anyone works on fixing this, please be aware that you do not need to log in to LoL. You can just run C:\Riot Games\League of Legends\Game\League of Legends.exe - if it pops up a message that you need to log in first, it is working; if it pops up a System Error message, it is broken. This makes testing much faster. -- 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=49025 --- Comment #12 from aguertin+wine(a)aguertin.net --- I think this is due to wow64cpu.dll?? My logs are showing that before a55fee removed get_builtin_fullname, get_builtin_fullname only ever had to get a fullname for ntdll and wow64cpu.dll. a55fee set a fullname for ntdll, but didn't make any changes to wow64cpu.dll, so it now gets passed to alloc_module without its fullname? -- 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=49025 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leslie_alistair(a)hotmail.com | |, z.figura12(a)gmail.com Component|-unknown |-unknown Product|Wine |Wine-staging --- Comment #13 from Alexandre Julliard <julliard(a)winehq.org> --- I guess it's wine-staging specific then. -- 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=49025 --- Comment #14 from aguertin+wine(a)aguertin.net --- Created attachment 67412 --> https://bugs.winehq.org/attachment.cgi?id=67412 patch (applies after wine staging) Thanks for pointing out that this comes from wine staging! The attached patch, which applies after wine staging, gets the game running again at least through wine-5.8. (It appears something else regressed and it does not run in wine-5.10. I will file a new bug for that once I bisect.) I'm not familiar with how to submit a patch to staging - hopefully this is sufficient to show what needs to be changed! -- 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=49025 --- Comment #15 from Simon the Sorcerer <sur3(a)gmx.de> --- It needs to be fixed in this patch then: https://github.com/wine-staging/wine-staging/blob/master/patches/wow64cpu-Wo... -- 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=49025 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #16 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Thanks. This is now fixed. https://github.com/wine-staging/wine-staging/commit/eb4f9db59c29b92131b9d0de... -- 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=49025 Gijs Vermeulen <gijsvrm(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |eb4f9db59c29b92131b9d0de352 | |00b9abf1d394a -- 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=49025 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #17 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Closing bugs fixed in Staging 5.15. -- 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=49025 --- Comment #18 from Simon the Sorcerer <sur3(a)gmx.de> ---
Closing bugs fixed in Staging 5.15.
I thought this was already fixed in Staging 5.11? o.O -- 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=49025 --- Comment #19 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Simon the Sorcerer from comment #18)
Closing bugs fixed in Staging 5.15.
I thought this was already fixed in Staging 5.11? o.O
Hello, Yes it was, but the bug report needed to be closed too and it has been done on release of staging 5.15. This is only a time reference for the records. 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.
https://bugs.winehq.org/show_bug.cgi?id=49025 Sjoer van der Ploeg <sfjuocekr(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sfjuocekr(a)gmail.com --- Comment #20 from Sjoer van der Ploeg <sfjuocekr(a)gmail.com> --- Hey, sorry to necro a "fixed" issue but I'm looking for some help! https://github.com/lutris/wine/issues/95 https://github.com/M-Reimer/wine-lol/issues/78 I'm trying to apply the bug fixes for LoL to 6.11 and am currently stumped on a stack overflow as soon as the game wants to load a practice (or any other) match. Maybe someone with more knowledge about the issue could take a look at it? -- 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)
-
WineHQ Bugzilla