WINE_MONO_OVERRIDES=Microsoft.Xna.Framework.*,Gac=y,MonoGac=n works around it, so it seems to be an FNA bug.
If I'm not mistaken, I tested this again on a newer Proton and didn't get the memory leak. I'll make sure to test again here in the coming days, though.
It must have been fixed and regressed again.
In my local build, I see a hang, with "double free or corruption" in the log. In Proton Experimental, it shows up for a second and then crashes. In Proton 10.0-2 (beta), it works.
Based on the timing, the update to SDL3 and the SDL_GPU backend probably broke this.
Yep, FNA3D_FORCE_DRIVER=D3D11 also works around it.
LMAO????
proton 10.0-2x1 2025-10proton experimentalx1 2025-10SDL_GPUx1 2025-10WINE_MONO_OVERRIDES=Microsoft.Xna.Framework.*,Gac=y,MonoGac=n`x1 2025-10
Compatibility Report
System Information
23.3.0-devel (git-85a01d8fa0)I confirm:
Symptoms
The game immediately on boot starts eating up all available RAM and swap space. It eventually dips down into around the 6 FPS zone before eventually causing the system to halt. This is not the behavior exhibited under Windows. Windows 11 was able to play the game from start to finish without any issues.
Reproduction
Proton Log
steam-1072860.log