24
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Jan 2026
24 points (96.2% liked)
Linux Gaming
21779 readers
2 users here now
Gaming on the GNU/Linux operating system.
Recommended news sources:
Related chat:
Related Communities:
Please be nice to other members. Anyone not being nice will be banned. Keep it fun, respectful and just be awesome to each other.
founded 5 years ago
MODERATORS
Try starting steam from the terminal. A lot of diagnostic info gets printed to stdout and stderr, which you can scroll through after a crash. Search up anything that looks like a serious error, it might point you in the right direction.
Weirdly enough, it did work that time, but froze the game when I tried to exit. I tried another time and it didn't run the game and gave some errors like:
and
and then a long stacktrace. No idea what it means.
The
LD_PRELOADone is actually harmless and annoyingly spams everyone. Steam tries to preload the 32 and 64 bit overlay library into every process and depends on one or the other failing.The free assert is bad and likely related to the crash. The stacktrace might be interesting if you want to share it.
The only cause that comes to mind is something like a libc conflict between the game and your graphics driver. That's going to be annoying to diagnose/fix though.
Do you see any messages about gperftools? I had memory issues with another steam game (TF2) and it turned out to be a bug in gperftools.
I just grepped the log for gperftools and came up with nothing.