Fossilize is spamming warnings to my log

[konomikitten]

When I start Warframe on Steam I see the following lines in my journal log:

Mar 16 16:07:31 debian steam[6391]: Fossilize WARN: Graphics pipeline handle 0x00007f23609a8230 is not registered.                                    
Mar 16 16:07:31 debian steam[6391]: It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an ext
ension that is not recognized by Fossilize).

This generates an extremely large amount of messages:

$ sudo journalctl --boot=0 --output=cat --grep='Fossilize WARN: Graphics pipeline handle .* is not registered' | wc -l
20085

So much in fact that journal reports that it has suppressed messages:

Mar 16 16:03:16 debian steam[6391]: Fossilize WARN: Graphics pipeline handle 0x00007f23586f0fb0 is not registered.
Mar 16 16:03:16 debian steam[6391]: It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize).
Mar 16 16:03:39 debian systemd-journald[493]: [🡕] Suppressed 11378 messages from user@1000.service
Mar 16 16:03:39 debian steam[6391]: Fossilize WARN: Graphics pipeline handle 0x00007f2368dc6d30 is not registered.
Mar 16 16:03:39 debian steam[6391]: It has either not been recorded, or it failed to be recorded earlier (which is expected if application uses an extension that is not recognized by Fossilize).

Could something be done about this?

I tried using setting the launch options to FOSSILIZE=0 %command% but this didn't stop the messages.

[konomikitten]

I was able to stop the spam in Steam by disabling Shader Pre-Caching in Downloads.

[felipenlunkes]

I'm having the same problem here, on Ubuntu 25.10. My hardware is:

CPU: Ryzen 7 9700x
GPU: ASUS Prime RX 9070 XT OC
Memory: 32 GB DDR5 6000 mt/s

I started noticing this today. Besides impacting game performance, it's creating over 10,000 logs of this type. As far as I know, I started noticing this today while playing Crimson Desert.

Using the parameters "%command% > /dev/null 2>&1" stops the logs from being generated/recorded. But it's complicated having to do this kind of workaround to be able to run the game properly. In addition, there's the split_lock that Steam stubbornly refuses to fix; I gave up and had to disable it at kernel startup.

In less than a minute, more than 4k logs were generated, which is enough to crash Gnome Logs.