Open DomiStyle opened 11 months ago
Hi there and thank you for the report. I have not been able to reproduce this so far either with my 7900xtx or my rdna2 iGPU. Do you know if it is tied to any special settings or such?
I assume this area shown below is the one that will crash in for you?
Yes, the area is correct. Settings are all Ultra except anti-aliasing on FXAA and Motion blur is off.
After some more testing I figured out that the game has a memory leak with DX11. Not sure what I did to trigger this but it now happens on DX11 every time I start the game, even on the main menu. Played for a full hour before that with no issues. The timing just aligned perfectly with loading into the third chapter.
Took a video of it here:
https://github.com/ValveSoftware/Proton/assets/975131/66358e26-5e39-4549-959c-29aefb490e10
The game in DX11 fills up the entire 32GB of RAM in just a few seconds, on DX12 it runs without issues.
@DomiStyle Hi there. I'm Back again. I have a suspicion it's probably this driver regression that was introduced with 23.1.6 https://gitlab.freedesktop.org/mesa/mesa/-/issues/9599 which can cause huge memory leaks in some games.
Yes, that sounds just like it.
I was able to resolve it by switching from Fedora Steam to the Flatpak version, which uses a different Mesa version. The issue mentioned above doesn't happen there.
Thanks for looking into it, I finished En Garde with no other issue.
Compatibility Report
System Information
I confirm:
steam-1654660_crash.log
Symptoms
The game (and Steam) crash at the start of chapter 3 when using the default DirectX 11 backend. DirectX 12 can be used as a workaround.
Reproduction