Kai Krakow

I don't think so because the Proton prefix won't contain any component of FreeTrack until you injected it, or does it? The problem is starting `opentracker-wrapper-wine.exe.so` in the first place....

@sthalik Here's the explanation: https://github.com/ValveSoftware/steam-runtime/issues/288#issuecomment-717954844 When injecting into Proton, it should check if `/usr/libexec/opentrack` actually exists, and if it doesn't, it needs to use `/run/host/usr/libexec/opentrack` instead.

So the solution is probably pretty simple: I can get away with installing opentrack to `/opt/opentrack` because that is outside `/usr` in the Steam Runtime container, and thus available as-is....

It works that way: ``` # pgrep -a opentrack 683657 /usr/bin/opentrack 685429 Z:\opt\opentrack\libexec\opentrack\opentrack-wrapper-wine.exe.so ``` If you're curious, here's what the build script looks like: https://github.com/gentoo/gentoo/pull/37646

@tdaven Does your kernel have /proc/pressure/memory? Does this happen while fossilize is background processing the shaders (Steam is idle) or foreground processing shaders (starting a game with the Vulkan shaders...

If you `watch cat /proc/pressure/{memory,io}`, do these values raise before the problem hits? Because then fossilize should throttle itself down by putting some threads into "stopped" phase... I've had a...

> I'm having the same problem. The memory usage is shared between processes. You need to look at the PSS size, or consider shared memory usage, too.

Lately, I found that KDE baloo may fight over resources with fossilize. Are you running KDE with baloo? Try stopping it and see if it helps.

I think this is because fossilize uses more threads if it starts working in the foreground - that is, if you start the game and Steam shows the progress dialog...

The errors went away for me after I compiled the `algif_hash` and `algif_skcipher` modules into the kernel. All the logged errors from above (`journalctl -f`) went away for me then....