Getting the same error when trying to launch palworld (it was fine yesterday):
Steam client version (build number or date): 1726604483
Distribution (e.g. Ubuntu): Ubuntu (KDE)
Opted into Steam client beta?: [Yes/No] No
Have you checked for system updates?: [Yes/No] Yes
GPU: AMD 7900xtx
Fossilize INFO: Setting autogroup scheduling.
***** OUT OF MEMORY! attempted allocation size: 1701012798 ****
src/tier0/memstd.cpp (3033) : OUT OF MEMORY
src/tier0/memstd.cpp (3033) : OUT OF MEMORY
src/tier0/memstd.cpp (3033) : Fatal assert; application exiting
src/tier0/memstd.cpp (3033) : Fatal assert; application exiting
assert_20240927181108_35.dmp[8023]: Uploading dump (out-of-process)
/tmp/dumps/assert_20240927181108_35.dmp
assert_20240927181108_35.dmp[8023]: Finished uploading minidump (out-of-process): success = yes
assert_20240927181108_35.dmp[8023]: response: CrashID=bp-21507732-ec5d-43cb-9ce3-bb1852240927
assert_20240927181108_35.dmp[8023]: file ''/tmp/dumps/assert_20240927181108_35.dmp'', upload yes: ''CrashID=bp-21507732-ec5d-43cb-9ce3-bb1852240927''
clearing download cache didn't help but after uninstalling and reinstalling the game the error seems gone, must have been some corruption somewhere
Have the exact same problem:
When I start steam and try to start e.g. Baldur's Gate 3 while shader pre-caching steam crashes.
This is the log from journalctl:
Okt 09 18:11:42 Cats steam[4319]: wine: using kernel write watches, use_kernel_writewatch 1.
Okt 09 18:11:42 Cats steam[4319]: fsync: up and running.
Okt 09 18:11:42 Cats steam[4319]: wine: using kernel write watches, use_kernel_writewatch 1.
Okt 09 18:11:42 Cats steam[4319]: wine: using kernel write watches, use_kernel_writewatch 1.
Okt 09 18:11:42 Cats steam[4319]: wine: using kernel write watches, use_kernel_writewatch 1.
Okt 09 18:11:42 Cats steam[4319]: wine: using kernel write watches, use_kernel_writewatch 1.
Okt 09 18:11:43 Cats steam[4319]: wine: using kernel write watches, use_kernel_writewatch 1.
Okt 09 18:11:43 Cats steam[4319]: wine: using kernel write watches, use_kernel_writewatch 1.
Okt 09 18:11:43 Cats steam[4319]: wine: using kernel write watches, use_kernel_writewatch 1.
Okt 09 18:11:43 Cats steam[4319]: wine: using kernel write watches, use_kernel_writewatch 1.
Okt 09 18:11:43 Cats steam[4319]: wine: using kernel write watches, use_kernel_writewatch 1.
Okt 09 18:11:44 Cats steam[4319]: wine: using kernel write watches, use_kernel_writewatch 1.
Okt 09 18:11:45 Cats steam[4319]: Fossilize INFO: Setting autogroup scheduling.
Okt 09 18:11:49 Cats steam[4319]: Fossilize INFO: Setting autogroup scheduling.
Okt 09 18:11:54 Cats steam[4319]: Fossilize INFO: Setting autogroup scheduling.
Okt 09 18:11:55 Cats steam[4319]: ***** OUT OF MEMORY! attempted allocation size: 1717790274 ****
Okt 09 18:11:55 Cats steam[4319]: src/tier0/memstd.cpp (3033) : OUT OF MEMORY
Okt 09 18:11:55 Cats steam[4319]: src/tier0/memstd.cpp (3033) : OUT OF MEMORY
Okt 09 18:11:55 Cats steam[4319]: src/tier0/memstd.cpp (3033) : Fatal assert; application exiting
Okt 09 18:11:55 Cats steam[4319]: src/tier0/memstd.cpp (3033) : Fatal assert; application exiting
Okt 09 18:11:55 Cats assert_20241009181155_35.dmp[6887]: Uploading dump (out-of-process)
/tmp/dumps/assert_20241009181155_35.dmp
Okt 09 18:11:55 Cats steam[4319]: assert_20241009181155_35.dmp[6887]: Uploading dump (out-of-process)
Okt 09 18:11:55 Cats steam[4319]: /tmp/dumps/assert_20241009181155_35.dmp
Okt 09 18:11:55 Cats kded6[1943]: Service ":1.100" unregistered
Okt 09 18:11:57 Cats assert_20241009181155_35.dmp[6887]: Finished uploading minidump (out-of-process): success = yes
Okt 09 18:11:57 Cats steam[4319]: assert_20241009181155_35.dmp[6887]: Finished uploading minidump (out-of-process): success = yes
Okt 09 18:11:57 Cats steam[4319]: assert_20241009181155_35.dmp[6887]: response: CrashID=bp-81d167fb-6ca6-4ce2-a4f6-e3af02241009
Okt 09 18:11:57 Cats steam[4319]: assert_20241009181155_35.dmp[6887]: file ''/tmp/dumps/assert_20241009181155_35.dmp'', upload yes: ''CrashID=bp-81d167fb-6ca6-4ce2-a4f6-e3af02241009''
Okt 09 18:11:57 Cats assert_20241009181155_35.dmp[6887]: response: CrashID=bp-81d167fb-6ca6-4ce2-a4f6-e3af02241009
Okt 09 18:11:57 Cats assert_20241009181155_35.dmp[6887]: file ''/tmp/dumps/assert_20241009181155_35.dmp'', upload yes: ''CrashID=bp-81d167fb-6ca6-4ce2-a4f6-e3af02241009''
Edit: This is not occuring for Deadlock. Have not tested other games than those two yet.
Hello again, I hope this issue is able to gain more traction with a bit more info:
I just re-tested this with a fresh installation of plain-old standard Ubuntu 24.04 from the latest LTS installation iso on the same hardware with nothing but Steam installed.
The exact same issue is occuring there aswell - trying to start Baldur's Gate 3 does not result in BG3 starting but Steam crashing with the exact same errors in the journal.
I have this issue, it happens whenever games gets updated. Shader pre-caching is disabled. I have about 190GB of ram so it's certainly not my machine. Are we hitting the limit of the 32 bits client?
The issue does not happen in steam big picture mode.
Correction: It doesn't happen when running under gamescope, which I use with big picture mode.
My steam decided it doesn't even want to start anymore, unless I use gamescope. This untenable. Crash on start, crash on quitting a game, crash on updating or installing games. What is it about gamescope that make steam behave properly?
I think I found the problem: I set the default stack size to 128000 in /etc/limits.d. It was fine since I have a ton of RAM, except for a 32 bit program of course. I don't know why it isn't a problem under gamescope, I assume it must be setting a new stack size limit. I will leave the limit to default and set it only if needed.
I think I found the problem: I set the default stack size to 128000 in
/etc/limits.d. It was fine since I have a ton of RAM, except for a 32 bit program of course. I don't know why it isn't a problem under gamescope, I assume it must be setting a new stack size limit. I will leave the limit to default and set it only if needed.
Thank you kind internet stranger. This is absolutely it.
Why increasing the processes stack size causes the program to crash? That's so weird. I wasn't even running out of memory.
I think I found the problem: I set the default stack size to 128000 in
/etc/limits.d. It was fine since I have a ton of RAM, except for a 32 bit program of course. I don't know why it isn't a problem under gamescope, I assume it must be setting a new stack size limit. I will leave the limit to default and set it only if needed.Thank you kind internet stranger. This is absolutely it.
Why increasing the processes stack size causes the program to crash? That's so weird. I wasn't even running out of memory.
Because 32 bits program are limited to 4GB of memory on your 64 bits kernel. In my case the stack size was set to 125MB, so every single thread would take at least this much memory. With a 32 cores system, you can imagine how quickly that 4GB gets depleted.
Same error happens to me.
Steam starts just fine, but as soon as I enable shader pre-caching and background processing for it, it crashes with this terminal output:
Fossilize INFO: Setting autogroup scheduling.
Fossilize INFO: Setting autogroup scheduling.
Fossilize INFO: Setting autogroup scheduling.
***** OUT OF MEMORY! attempted allocation size: 1680879938 ****
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_20260627211045_79.dmp[53828]: Uploading dump (out-of-process)
/tmp/dumps/assert_20260627211045_79.dmp
My system:
Operating System: EndeavourOS
KDE Plasma Version: 6.7.1
KDE Frameworks Version: 6.27.0
Qt Version: 6.11.1
Kernel Version: 7.0.12-zen1-1-custom-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
Memory: 32 GiB of RAM (30.6 GiB usable)
Graphics Processor 1: AMD Radeon 780M Graphics
Graphics Processor 2: AMD Radeon RX 7700S
Manufacturer: Framework
Product Name: Laptop 16 (AMD Ryzen 7040 Series)
Same error happens to me.
In my case, the culprit was a file called steam_dev.cfg with the content
unShaderBackgroundProcessingThreads 16
that I created because I tried to boost shader compilation performance.
After removing the file and restarting steam, I can pre-compile shaders again.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
So my client keeps crashing between 45 seconds and 40 minutes after launch. The only log I get is
While my system ram does not appear to actually be affected I can see using top that 2 steamwebhelpers request all my of free memory with each requesting over 48G of VIRT ram. They can sit this way for awhile before crashing, I assume by me doing any task that might actually use the remaining ram.