ValveSoftware
FBC: Firebreak (2272540)
Compatibility Report
- Name of the game with compatibility issues: FBC: Firebreak
- Steam AppID of the game: 2272540
System Information
- GPU: GeForce RTX 3080 Lite Hash Rate
- Video driver version: nvidia
575.64 - Kernel version:
6.12.33 - Link to full system information report as Gist: https://gist.github.com/Athanasius/dffbd8e21feb82da8a41535e925530ba
- Proton version: "Proton Hotfix", version file says
1746128130 hotfix-20250501
I confirm:
- [X] that I haven't found an existing compatibility report for this game.
- [X] that I have checked whether there are updates for my system available.
Symptoms
The game does actually run, but there's some sort of memory leak. It starts at a little under 4GiB for the affected process, and then during a Job (mission) it gradually increases, ending on around 8 GiB, a small dip between Jobs, and then by the end of the second Job it increases to around 13GiB, and during the third it reached as high as 18 GiB, and then the OOM killer kicked in and took the game down.
Graph of the 'RSS' value for the process: https://miggy.org/games/FBC-Firebreak/firebreak-linux-memory-usage.png
This does not happen in Windows 11 Pro. Memory usage doesn't even hit 8 GiB. Same graphical settings, that's with nvidia drivers 576.80. Obviously it could still be a game bug, but this points more at Proton, or supporting libraries.
Reproduction
Happens every time I play in Linux.
The game fails to fully start under Proton Experimental 1749849620 experimental-10.0-20250612c.
It starts playing the initial splash screen then crashes. I sent the crash report.
I tried GE-Proton10-4 (by unarchiving it in compatibilittools.d), and that also seems to exhibit this memory leak, but perhaps slower. Not had chance to do back to back Level 3 Jobs yet to recreate the same circumstances.
Memory leak still happening with GE-Proton10-8, maybe slower than that graph, but the game got OOM-killered again.
Also memory use was up to 18GiB by the end of 3 Jobs using Proton 9.0-4.
This is with nvidia drivers 575.64.03 now.
I know others on Linux running this game don't have the issue, so presumably there's some setting or hardware/drivers difference tickling it in my case.