Steam Crashes with Out of Memory

Steam has been crashing with out of memory errors since yesterday. RAM usage is fine I’m only using 7GB out of 64GB. No changes since I last used steam and issues started arising. I was in-game on dota watching my friend play then closed it and put the PC to sleep. The next day steam crashes on launch.

\[2026-10-10 20:57:55.436\] \[MANGOHUD\] \[info\] \[blacklist.cpp:86\] process 'vulkandriverquery' is blacklisted in MangoHud
Fossilize INFO: Setting autogroup scheduling.
Proton: Upgrading prefix from 5.5-GE-1 to 4.2-2 (/home/zangoku/.local/share/Steam/steamapps/compatdata/0)
Proton: Prefix has an invalid version?! You may want to back up user files and delete this prefix.
Desktop state changed: desktop: { pos:    0,   0 size: 6400,1440 } primary: { pos: 1920,   0 size: 2560,1440 }
Caching cursor image for text, size 24x24, serial 132, cache size = 0
\*\*\*\*\* OUT OF MEMORY! attempted allocation size: 1647522115 \*\*\*\*
src/tier0/memstd.cpp (3039) : OUT OF MEMORY
src/tier0/memstd.cpp (3039) : OUT OF MEMORY
src/tier0/memstd.cpp (3039) : Fatal assert; application exiting
src/tier0/memstd.cpp (3039) : Fatal assert; application exiting
assert_20261010205800_43.dmp\[13729\]: Uploading dump (out-of-process)
/tmp/dumps/assert_20261010205800_43.dmp
{26-10-10 20:58}whateverthisis:\~ zangoku% wine: configuration in '/home/zangoku/.local/share/Steam/steamapps/compatdata/0/pfx' has been updated.
assert_20261010205800_43.dmp\[13729\]: Finished uploading minidump (out-of-process): success = yes
assert_20261010205800_43.dmp\[13729\]: response: CrashID=bp-ace5ac40-0646-462a-913a-e0a1f2261010
assert_20261010205800_43.dmp\[13729\]: file ''/tmp/dumps/assert_20261010205800_43.dmp'', upload yes: ''CrashID=bp-ace5ac40-0646-462a-913a-e0a1f2261010''
\[2026-10-10 20:58:11.138\] \[MANGOHUD\] \[info\] \[cpu.cpp:636\] hwmon: using input: /sys/class/hwmon/hwmon5/temp2_input
Fossilize INFO: Overriding serialization path: "/home/zangoku/.local/share/Steam/shader_cache_temp_dir_d3d11_64/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize INFO: engineVersion 4194307 is too low for pEngineName DXVK. Skipping.
Fossilize INFO: engineVersion 4194307 is too low for pEngineName DXVK. Skipping.
Fossilize WARN: Sampler handle 0x00000000a9fbc2c0 is not registered.
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).
Fossilize WARN: Descriptor set layout handle 0x00000000aa1af140 is not registered.
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).
Fossilize WARN: Pipeline layout handle 0x00000000aa1fb7f0 is not registered.
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).
Fossilize WARN: Pipeline layout handle 0x00000000aa1fb7f0 is not registered.
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).
Initializing D3D11.```

[2026-10-10 21:13:25.662] [MANGOHUD] [info] [blacklist.cpp:86] process 'vulkandriverquery' is blacklisted in MangoHud
[2026-10-10 21:13:26.166] [MANGOHUD] [info] [blacklist.cpp:86] process 'vulkandriverquery' is blacklisted in MangoHud
Fossilize INFO: Setting autogroup scheduling.
Desktop state changed: desktop: { pos: 0, 0 size: 6400,1440 } primary: { pos: 1920, 0 size: 2560,1440 }
Caching cursor image for text, size 24x24, serial 132, cache size = 0
***** OUT OF MEMORY! attempted allocation size: 1647522115 ****
src/tier0/memstd.cpp (3039) : OUT OF MEMORY
src/tier0/memstd.cpp (3039) : OUT OF MEMORY
src/tier0/memstd.cpp (3039) : Fatal assert; application exiting
src/tier0/memstd.cpp (3039) : Fatal assert; application exiting
assert_20261010211331_43.dmp[22498]: Uploading dump (out-of-process)
/tmp/dumps/assert_20261010211331_43.dmp
{26-10-10 21:13}whateverthisis:~ zangoku% assert_20261010211331_43.dmp[22498]: Finished uploading minidump (out-of-process): success = yes
assert_20261010211331_43.dmp[22498]: response: CrashID=bp-d386af4b-e3a4-470b-b3d0-2c6fa2261010
assert_20261010211331_43.dmp[22498]: file ''/tmp/dumps/assert_20261010211331_43.dmp'', upload yes: ''CrashID=bp-d386af4b-e3a4-470b-b3d0-2c6fa2261010''
[2026-10-10 21:13:38.583] [MANGOHUD] [info] [cpu.cpp:636] hwmon: using input: /sys/class/hwmon/hwmon5/temp2_input
Fossilize INFO: Overriding serialization path: "/home/zangoku/.local/share/Steam/shader_cache_temp_dir_d3d11_64/fozpipelinesv6/steamapprun_pipeline_cache".
Fossilize INFO: engineVersion 4194307 is too low for pEngineName DXVK. Skipping.
Fossilize INFO: engineVersion 4194307 is too low for pEngineName DXVK. Skipping.
Fossilize WARN: Sampler handle 0x00000000adacf0e0 is not registered.
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).
Fossilize WARN: Descriptor set layout handle 0x00000000ada7de20 is not registered.
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).
Fossilize WARN: Pipeline layout handle 0x00000000adacf180 is not registered.
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).
Fossilize WARN: Pipeline layout handle 0x00000000adacf180 is not registered.
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).
Initializing D3D11.

So far I have tried updating everything, clearing caches: appcache, shaderscache, htmlcache, getting rid of the app manifest and corrupted folder as well as rebooting.

This is really strange to me. When I started my last gaming session today, I had recently ungraded to Proton-GE 11-7:

Proton: Upgrading prefix from GE-Proton11-5 to GE-Proton11-7

Are you really running a version of Proton that old???

I do have old version installed, but I mostly use the latest stable one and experimental for my games. Not sure why steam has a prefix and how to set its version.

Have you ever installed any Proton versions from outside of Steam? If so, try removing those to at least eliminate them from the equation.

Disable mangohud or update it to see if it makes any changes. I see errors for mangohud in your logs.

I get those as well. Just information, not errors.

I did some more digging and I found a github thread from over 6 years ago which mentioned disabling shader pre-caching. So I did that and it fixed the error, been running steam without crashes. I edited /.local/share/Steam/config/config.vdf and searched for ShaderCacheManagerthen I added "DisableShaderCache" "1" and I edited this one "EnableShaderBackgroundProcessing" "0" from 1 to 0.

I tried re-enabling it and it crashed again right away with the same error. How can I use shaders again without steam breaking?

As for proton it seemed to be because I cleaned up caches and it set the latest version once it managed to fully launch without crashing.

You don’t need Steam to manage shader caching; each game can do that on their own. I have it enabled in Steam, which does allow it to download some pre-compiled shaders, making processing of shaders a bit quicker.

It’s not a performance booster.

Longshot, but you could try removing the shader cache in /path/to/your/SteamLibrary/steamapps/shadercache & ~/.local/share/Steam/steamapps/shadercache

I tried clearing all of them and re-enabling the setting then it crashed again.

see this point

and