[Solved] Getting intermediate client crashes since Celeste release (Linux)

[nxa]

Since Celeste's release earlier this week, my game has been crashing seemingly randomly. Mind, I've played a considerable number of games since the initial release of the Old Gods update without issue. This issue has only occured since Celeste release. I'm using the Linux native version and have tried both with native vulkan and proton with dx11.

I've had games where there have been 4 crashes seemingly randomly and I've also crashed just testing things in my hideout (notably, not using Celeste, so it isn't inherently related to her model or kit). I've also re-watched replays of games where I've crashed and made it through the points (from my pown PoV) where the game crashed, suggessting it's not related necessarily to something on screen. It's also crashed while I was dead in base suggesting that it's not related to an action I'm taking.

Unfortunately the client instantly closes and there's seemingly no crash log in the game directory and I've got no note of anything in the system logs, so I've got nothing else to go off of.

I just tried running through Proton Experimental and it still crashes in the same manner so it may not necessarily be related to the Linux native client.

 

[envil]

I have only managed to play like 5 matches since then but no issues at all during those. Do your other games still work fine? If you tried dx11 I assume you actually mean the default Proton version and not Native (which afaik does not exist)?

 

[nxa]

Still having the same crashes after the apollo update, both with native linux vulkan and dx11 under proton. Just straight crash to desktop, no logging.

 

[nxa]

Tried disabling the steam overlay per another thread and ist seems to have reduced the amount of crashes (which could ultimately just be coincidence) but I do have crash dumps now at least. There are a number of references to localization issues and I did start to notice that I was in the shop menu or build editor the previous two crashes, but that could also be nothing.

 

[arin fairfax]

I didn't want to pollute the forum with another post about the same subject so I am writing here. This past update has been awful. Constant game crashes, unplayable framerates, FPS all over the place with sometimes 120+ and sometimes 20 for a while then back to 120+. The worst is audio. It's a hit or miss. Sometimes just works, sometimes it's like I am listening the game from someone else's mic.

 

[envil]

What are your setups? (Distro, hardware, kernel and driver versions etc)

This could be useful to know to see if there's anything common. For myself the game still runs flawless and I haven't had a single crash ever.

There also was various posts about people crashing with corrupted files and the like on Windows, maybe it's related to that too and it just doesn't manage to show the message.

 

[nxa]

OS: Arch Linux (kernel Linux 6.18.9-arch1-2)
DE: KDE Plasma 6.5.5
GPU: AMD Radeon RX 7900XT (driver Mesa 25.3.5-arch1.1)
CPU: Intel i5-12600k

I've tried verifying files a couple times now which has not alleviated the crashing. Of note, I did not do any system updates between when I was playing before (graves, rem, silver releases) and when the crashes started (celeste release)

 

[envil]

Curious as mine is very similar.

OS: Arch Linux (6.18.8-arch2-1) (cmdline: mitigations=off pcie_aspm=off)
DE: KDE Plasma 6.5.5
GPU: AMD RX 7900 XTX (Mesa 25.3.5-arch1.1)
CPU: AMD 5800X3D
RAM: 64GB

I still haven't had a single crash since playing the game (20+ matches since Celeste I guess). One thing I'd suggest is running a memtest just to ensure the ram is fine and check for any Bios updates as some of those Intel CPUs were kinda buggy from what I recall.

I also have

DXVK_ASYNC=1 PROTON_FSR4_UPGRADE=1 %command%

as launch option in Steam but I don't think that makes any difference (async is default afaik and I don't use FSR).

 

[nxa]

I tried playing on a fresh Arch install with only KDE Plasma, Steam, and Discord installed and experienced the same crashes with the same "accessviolation".mdmp files. I also tried using the git branches of the Mesa driver and Vulkan-radeon and it still crashed.

I'm somewhat inclined to think it may be hardware related, but as I've experienced no crashes in other games and have run GPU stress tests and memtests without any errors, I'm not entirely sure.

The console log still just spams
[Localization System] CLocalize::ConstructString failed to localize: #CitadelItemSlotFavorites
[Localization System] CLocalize::ConstructString failed to localize: #CitadelItemSlotFavorites
[Localization System] CLocalize::ConstructString failed to localize: #CitadelItemSlotFavorites
but that could just normal (or expected at least?)

It's also possible it's specific to something in Celeste's kit, as I've pretty much gotten her every game the last few days, but that's just speculation.

 

[envil]

I do have those console log messages as well, but it does not spam it. They only appear once more or less.

There is quite a few other crash posts around here so it's kinda hard to tell. Others mentioned crashing when they press a certain key while being in a party and the like.

If you feel like messing around there some random stuff you could try to see if it makes any difference:
- Disable pcie_aspm (see my kernel cmdline from above)
- Disable virtualization support in the bios
- Disable cpu turbo boost in bios

But no telling if this will do anything or not.

 

[nxa]

Tried some of your suggestions above and also ended up trying to play on a windows installation and I still received the exact identical crash and mdmp file, so I'm out of ideas.

I also did not realize that steam had started defaulting the "Steam Play compatability for all titles" setting to "on" at some point so I did not realize it wasn't running a native version, it was using proton all along, so that's neat. (I also tried using proton GE after realizing this and was still having issues.)

I'm further inclined to think it's a hardware issue but given I'm not having trouble in any other games and given I wasn't having trouble when I was playing before the Celeste update, I'm just not sure.

 

[nxa]

I believe it ultimately ended up being due to a faulty XMP profile setting on my memory (which for whatever reason was only causing issues with deadlock and didn't produce errors in memtest?), but after much troubleshooting I have finally resolved the crashes. Thanks for the help as well, envil.