https://bugs.winehq.org/show_bug.cgi?id=40265
Bug ID: 40265 Summary: Payday 2 Randomly Crashes Product: Wine Version: 1.9.5 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: kernel32 Assignee: wine-bugs@winehq.org Reporter: gordan@bobich.net Distribution: Other
Created attachment 53883 --> https://bugs.winehq.org/attachment.cgi?id=53883 Payday 2 Crash Backtrace
Payday 2 randomly crashes. Wine build is standard 1.9.5 from PlayOnLinux. Backtrace attached.
https://bugs.winehq.org/show_bug.cgi?id=40265
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|kernel32 |-unknown
https://bugs.winehq.org/show_bug.cgi?id=40265
--- Comment #1 from Gordan Bobic gordan@bobich.net --- Created attachment 53889 --> https://bugs.winehq.org/attachment.cgi?id=53889 Another Payday 2 Crash Backtrace
https://bugs.winehq.org/show_bug.cgi?id=40265
--- Comment #2 from Gordan Bobic gordan@bobich.net --- Created attachment 53890 --> https://bugs.winehq.org/attachment.cgi?id=53890 And Another Payday 2 Crash Backtrace
https://bugs.winehq.org/show_bug.cgi?id=40265
--- Comment #3 from Gordan Bobic gordan@bobich.net --- Created attachment 53891 --> https://bugs.winehq.org/attachment.cgi?id=53891 PD2 crash backtrace
https://bugs.winehq.org/show_bug.cgi?id=40265
fjfrackiewicz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fjfrackiewicz@gmail.com
--- Comment #4 from fjfrackiewicz@gmail.com --- You might want to submit that bug to the Play On Linux guys as POL is not supported here according to the guidelines:
See the "When to report a bug" section.
Can you try running Payday2 without using POL?
https://bugs.winehq.org/show_bug.cgi?id=40265
--- Comment #5 from Gordan Bobic gordan@bobich.net --- I'll see what I can do about trying it without the PoL wrapper, but does that also mean not using the PoL WINE binaries? The problem is that the latest WINE binaries for CentOS 7.x in EPEL are 1.8.1, and building i686 wine (and generally i686 packages) on x86-64 CentOS is problematic.
And WINE project doesn't provide CentOS binaries, only bleeding edge Fedora ones which have dependencies that don't exist in EL7.
I'll try it using WINE 1.8.1 from EPEL.
https://bugs.winehq.org/show_bug.cgi?id=40265
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #6 from winetest@luukku.com --- (In reply to Gordan Bobic from comment #5)
I'll see what I can do about trying it without the PoL wrapper, but does that also mean not using the PoL WINE binaries? The problem is that the latest WINE binaries for CentOS 7.x in EPEL are 1.8.1, and building i686 wine (and generally i686 packages) on x86-64 CentOS is problematic.
And WINE project doesn't provide CentOS binaries, only bleeding edge Fedora ones which have dependencies that don't exist in EL7.
I'll try it using WINE 1.8.1 from EPEL.
Since you opened this bug against POL build and its a bit problemetic to build wine on centos I would suggest you to try other wine versions via POL. This bug report really dont belong here...
Even it would be fixed already, we shouldnt mark it as fixed since the report was used via POL.
https://bugs.winehq.org/show_bug.cgi?id=40265
minion minion.procyk@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |minion.procyk@gmail.com
--- Comment #7 from minion minion.procyk@gmail.com --- Game still crashes pretty often and (somewhat) randomly. It most often crashes after joining enough peoples' lobbies or after loading different maps or attempting to start gameplay from the post-lobby screen (screen where everyone readies up).
This behaviour can be observed with latest wine, wine-staging, proton. It's unfortunate because it's hard to enjoy the game when it crashes every ~3rd map. I've also tried various debug channels to find a clue, but have been unsuccessful. All i can tell is when it freezes, it spams NtQuerySystemInformation with stack traces until you force close, and when it crashes it calls the same method a handful of times with stack traces and then closes.