protonscr

Unity game crashes along with DE, and the file system gets corrupted.

dxvkclosed not our bug
doitsujin/dxvk#4600 · opened 2025-01-10 by lufog · updated 2025-01-10 · 9 comments · github
1 matching comments, n / p to jump
Llufog 2025-01-10 github

I have a strange problem when I try to run a certain Unity game in Wine + DXVK, the game crashes, and after the game, everything crashes (DE, systemd, etc.) and the file system gets corrupted. The problem is reproducible, out of three attempts to run the game, all 3 times I corrupted my FS, once I even had to boot from a flash drive to fix it.

The game always crashes when trying to load a texture in the main menu, until it is loaded (white) everything is fine, as soon as it loads, the game crashes. I am not sure if this is a problem with DXVK, Wine, or something with the game itself (its previous version works without problems).

Software information

NSFW

Yokai Art: Night Parade of One Hundred Demons v2.5.1.004

System information

  • GPU: Geforce 1660 (NV168)
  • Driver: nouveau (linux 6.12.8) mesa/nvk 24.3.3
  • Wine version: wine-staging-wow64 10.0rc4 (tried on 9.x too)
  • DXVK version: dev build (tried 2.5.2 too)

Apitrace file(s)

Google Drive

Log files

game.log
backtrace.txt

SSid127 2025-01-10 github

Could you describe the file system corruption further?
Also, the apitrace requires me to request access (which I did)

WWinterSnowfall 2025-01-10 github

DXVK pretty much can't crash your desktop environment and definitely can't cause any FS corruption. The underlying Vulkan driver that is used with it possibly can (at least crash your DE by crashing the entire stack), so I guess the first thing to try is to see if the problem goes away with the proprietary Nvidia driver.

Llufog 2025-01-10 github

@Sid127,

Could you describe the file system corruption further?

The first time I tried to launch the game (on Wine 9.22), the game crashed and Unity Crash Handler and WineDbg windows appeared, after closing them, DE crashed, and I was thrown into a console with some errors from systemd (as far as I understand, some critical parts of systemd crashed). After rebooting, I could not boot into the OS, I only got to the console in which there were errors about missing or damaged files (I don't remember exactly). What helped me was booting from a flash drive, from which I checked FS.

The second time, DE simply crashed, after rebooting, fsck started searching for/correcting errors. After that, I got into GDM, but could not get further because of a damaged libwayland (I think -client).so file. Reinstalling the wayland package helped. By the way, the chromium profile was damaged, I tried to launch it before DE crashed.

The third time, systemd crashed again, there was fsck scanning again during boot, but this time I booted successfully.

Only by these signs I assume that something is happening with the FS. Maybe I'm wrong, and the FS problems are just a symptom that occurs due to the crash of some critically important system component. The problem is always reproducible, if there is a possibility to make some dumps, I can try.

Also, the apitrace requires me to request access (which I did)

sorry, I completely forgot that by default files on GD are not accessible. I changed the access settings.

Llufog 2025-01-10 github

DXVK pretty much can't crash your desktop environme

I'll try to test the game with the proprietary driver a bit later. It's strange that an older version of the same game works without problems. And any other games (like Vampire Survivors/VotV/STALKER) work fine.

~Now I want to try to run the game in the new wine prefix, without DXVK.~

I don't know how useful this information is, but in Wine prefix without DXVK, the game works without crashes. So maybe the problem is in NVK? Because as far as I understand, DirectX built into Wine uses OpenGL?.. (I don't really understand this, maybe I wrote something stupid)

SSid127 2025-01-10 github

Purchased the game to test it out, I am unable to reproduce the issue with a variety of configurations on Arch Linux

  • Mesa git, 6.13-rc6, Proton Experimental, Plasma Wayland
  • Mesa 24.3.3, 6.13-rc6, Wine staging 9.22, DXVK 2.5.2, Plasma Wayland
  • Mesa 24.3.3, 6.12.8, Wine staging 9.22, DXVK 2.5.2, Plasma Wayland
  • Mesa 24.3.3, 6.12.8, Wine staging 9.22, DXVK 2.5.2, Gnome Wayland

I'm also running BTRFS, which should be most prone to FS corruption if the masses are right.
Screenshot_20250110_164128

Llufog 2025-01-10 github

@Sid127, tried in a new empty Wine prefix, only with corefonts and DXVK 2.5.2, the problem reproduced. Apparently the problem only occurs on my hardware. I'll close the issue until I find some additional useful information, or at least recheck everything with the proprietary driver.

Llufog 2025-01-10 github

@Sid127, @WinterSnowfall, it turned out to not be a DXVK issue after all. I was able to reproduce it with wine's built-in libraries by simply switching the renderer to vulkan (HKEY_CURRENT_USER\Software\Wine\Direct3D renderer vulkan). Sorry for wasting your time. I should have looked into the problem more thoroughly before opening an issue.

WWinterSnowfall 2025-01-10 github

No worries. It was pretty clear from the start dxvk can't really cause something that serious, but of course it can expose problems in the underlying driver stack.

AAmmar-Sadaoui 2025-01-10 github

you should check your disk health

i think your disk is dying, and sometimes there are no errors to indicate that in SMART

Proton versions