https://bugs.winehq.org/show_bug.cgi?id=49518
Bug ID: 49518 Summary: Grim Dawn leaks shared memory after upgrade to Wine 5.12 Product: Wine Version: 5.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: andysem@mail.ru Distribution: ---
After a few hours of gameplay Grim Dawn consumes around 10 GiBs of shared memory, as reported by KDE System Monitor (KSysGuard). At that point the game stopped running because of:
err: DxvkSubmissionQueue: Failed to sync fence: VK_ERROR_DEVICE_LOST err: DxvkSubmissionQueue: Command submission failed: VK_ERROR_DEVICE_LOST
The game audio continued to play and it sounded like it was reacting to keypresses, but the display image was frozen.
I'm not sure what kind of memory is reported as shared memory, but given that it ends with a DXVK error, it looks like it may be GPU memory.
This did not happen with Wine 5.10.
Kubuntu 20.04 x86_64, Nvidia driver 440.66.17 (RTX 2080 Ti with 11 GiB VRAM), DXVK 1.7.
https://bugs.winehq.org/show_bug.cgi?id=49518
--- Comment #1 from Andy andysem@mail.ru --- Additionally, with Wine 5.12 I'm occasionally seeing a graphical glitch, which looks like a black screen that moves into the scene (upwards in Z axis), gradually revealing it as it passes different objects, like trees, character models and terrain. It's as if there is a moving Z threshold, after which nothing is drawn.
The game is 1.1.7.1, GOG version.
https://bugs.winehq.org/show_bug.cgi?id=49518
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #2 from joaopa jeremielapuree@yahoo.fr --- Please, talk about only one problem per report (that's bugzilla policy) For the regression, please do a regression test: https://wiki.winehq.org/Regression_Testing
https://bugs.winehq.org/show_bug.cgi?id=49518
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- DXVK is a third-party project and therefore not supported in this bug tracker. Please use wined3d or report bugs against the DXVK project.
https://bugs.winehq.org/show_bug.cgi?id=49518
--- Comment #4 from Andy andysem@mail.ru --- Given that I'm only changing Wine versions between working and not working setups, I don't think DXVK is the culprit. Therefore I'm reporting a Wine bug. If it turns out that DXVK is the source of the problem, I will report the bug there.
https://bugs.winehq.org/show_bug.cgi?id=49518
--- Comment #5 from Zebediah Figura z.figura12@gmail.com --- Changes in one component may expose bugs in another. This may be a bug in upstream Wine, or in DXVK. It's not necessarily trivial to determine which.
Trying to reproduce the bug with wined3d would probably be a good idea.
https://bugs.winehq.org/show_bug.cgi?id=49518
--- Comment #6 from Andy andysem@mail.ru --- I am not able to bisect to a single commit that introduced the breakage because Grim Dawn either doesn't start or doesn't load the saved game with most of the commits between 5.11 and 5.12. In particular, this is the kind of errors I'm getting:
err:virtual:virtual_map_ntdll couldn't load ntdll at preferred address 0x7bc00000 wine: failed to load ~/src/wine/tmp/64/dlls/ntdll/ntdll.dll error c0000018 0024:err:environ:run_wineboot failed to start wineboot c00000e5 err:virtual:virtual_map_ntdll couldn't load ntdll at preferred address 0x7bc00000 wine: failed to load ~/src/wine/tmp/64/dlls/ntdll/ntdll.dll error c0000018
Therefore, the breakage occurred somewhere between 6ff0bb786c43ac3348dec6a977feb36af8bc4bcf (which works) and c02b63fb60458ec750e5991a7491235861c40061 (which exhibits the black graphical glitch I described earlier).
Regarding the shared memory leak, I couldn't reproduce it during bisection testing, but I did see the same graphical glitch and the game eventually froze a few times with the same VK_ERROR_DEVICE_LOST error. So maybe the shared memory problem was just an unreliable byproduct of the problem.
https://bugs.winehq.org/show_bug.cgi?id=49518
Andy andysem@mail.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #7 from Andy andysem@mail.ru --- This seems to have been fixed in 5.13.
https://bugs.winehq.org/show_bug.cgi?id=49518
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 5.15.
-
WineHQ Bugzilla