Status update: nope, it still crashes. Definitely this is about the library view and not recording process itself.
Looks similar to my issue, steam UI crash, but still usable from system tray icon: https://github.com/ValveSoftware/steam-for-linux/issues/11449
Game recording disabled for all games.
Well in my case it is definitely related to game recording. Steam crashing when trying to render the section of the game view where latest recording should be.
Hello,
Please make sure you reproduce this with the latest beta, and provide a crash ID. Logs may be useful as well, but probably less so.
Similar issue, applies to Recordings & Screenshot view and Big Picture mode when viewing a game page. Segfaults when trying to load content. Reproducible by playing a game with Recording enabled and then trying to view any page with the recording content in it.
Full Steam Hardware report:
hardware-steam.txt
Recordings & Screenshots viewLogs: steam-logs-media-view.tar.gz
Terminal output, related to crash
crash_20241221225032_32.dmp[172809]: Uploading dump (out-of-process)
/tmp/dumps/crash_20241221225032_32.dmp
crash_20241221225032_32.dmp[172809]: Finished uploading minidump (out-of-process): success = yes
crash_20241221225032_32.dmp[172809]: response: CrashID=bp-941dbb12-4d83-4c1c-832b-df4fa2241221
crash_20241221225032_32.dmp[172809]: file ''/tmp/dumps/crash_20241221225032_32.dmp'', upload yes: ''CrashID=bp-941dbb12-4d83-4c1c-832b-df4fa2241221''
/home/user/.local/share/Steam/steam.sh: line 906: 172450 Segmentation fault (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@"
coredumpctl info 172450 :
PID: 172450 (steam)
...
Signal: 11 (SEGV)
...
Message: Process 172450 (steam) of user 1000 dumped core.
Stack trace of thread 172779:
#0 0x00000000efa225eb XDisplayString (libX11.so.6 + 0x215eb)
#1 0x00000000e029ebdd __vaDriverInit_1_22 (nvidia_drv_video.so + 0xdbdd)
#2 0x00000000e387133c vaInitialize (libva.so.2 + 0x733c)
#3 0x00000000e43dcfbe n/a (/home/user/.local/share/Steam/ubuntu12_32/libavutil.so.59 + 0x33fbe)
ELF object binary architecture: Intel 80386
coredumpctl debug 172450 :
...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/home/user/.local/share/Steam/ubuntu12_32/steam -srt-logger-opened'.
Program terminated with signal SIGSEGV, Segmentation fault.
Downloading 6.96 K source file /usr/src/debug/lib32-libx11/libX11-1.8.10/src/Macros.c
#0 0xefa225eb in XDisplayString (dpy=0x0) at /usr/src/debug/lib32-libx11/libX11-1.8.10/src/Macros.c:119
119 char *XDisplayString(Display *dpy) { return (DisplayString(dpy)); }
[Current thread is 1 (Thread 0xcdb77b40 (LWP 172779))]
Big Picture modeLogs: steam-logs-big-picture.tar.gz
Terminal output, related to crash:
crash_20241221225328_31.dmp[174437]: Uploading dump (out-of-process)
/tmp/dumps/crash_20241221225328_31.dmp
crash_20241221225328_31.dmp[174437]: Finished uploading minidump (out-of-process): success = yes
crash_20241221225328_31.dmp[174437]: response: CrashID=bp-4684c6ef-1e6d-4251-a43f-f1b522241221
crash_20241221225328_31.dmp[174437]: file ''/tmp/dumps/crash_20241221225328_31.dmp'', upload yes: ''CrashID=bp-4684c6ef-1e6d-4251-a43f-f1b522241221''
/home/user/.local/share/Steam/steam.sh: line 906: 174030 Segmentation fault (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@"
coredumpctl info 174030 :
PID: 174030 (steam)
...
Signal: 11 (SEGV)
....
Message: Process 174030 (steam) of user 1000 dumped core.
Stack trace of thread 174309:
#0 0x00000000f34f95eb XDisplayString (libX11.so.6 + 0x215eb)
#1 0x00000000e3ce6bdd __vaDriverInit_1_22 (nvidia_drv_video.so + 0xdbdd)
#2 0x00000000e734d33c vaInitialize (libva.so.2 + 0x733c)
#3 0x00000000e7eb8fbe n/a (/home/user/.local/share/Steam/ubuntu12_32/libavutil.so.59 + 0x33fbe)
ELF object binary architecture: Intel 80386
coredumpctl debug 174030 :
...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/home/user/.local/share/Steam/ubuntu12_32/steam -srt-logger-opened'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xf34f95eb in XDisplayString (dpy=0x0) at /usr/src/debug/lib32-libx11/libX11-1.8.10/src/Macros.c:119
119 char *XDisplayString(Display *dpy) { return (DisplayString(dpy)); }
[Current thread is 1 (Thread 0xd81fbb40 (LWP 174309))]
Hello @imaginaryPineapple,
Unfortunately we cannot reproduce. Can you run Help -> Steam Runtime Diagnostics and then send your logs please? (tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs)
This could be a problem with your 32 bit libva drivers, on Arch with NVidia you should have lib32-libva and lib32-mesa installed. You can check with pacman -Qs libva - I'm assuming Manjaro is the same.
I assume that if you bring up the overlay while recording, and place your cursor on the timeline to get thumbnails, you are crashing in the same way?
Also - do you have H.265 enabled in your settings? Your crash looks to be happening inside VAAPI initialization, which would mean it's trying to initialize for H.264 and use your integrated AMD GPU, which may not be what you intended.
Thanks,
I assume that if you bring up the overlay while recording, and place your cursor on the timeline to get thumbnails, you are crashing in the same way?
It does not, the thumbnails also show up properly. However, Steam crashed after I closed the game, producing segfault (11). Same message as before. Turning off Cloud Sync fixes this crash.
steam-logs.tar.gz
Steam Runtime Diagnostics
steam-runtime-info.txt
steam-runtime-info-logs.tar.gz
pacman -Qs libva
local/lib32-libva 2.22.0-1
Video Acceleration (VA) API for Linux (32-bit)
local/lib32-libva-intel-driver 2.4.1-2
VA-API implementation for Intel G45 and HD Graphics family (32-bit)
local/lib32-libva-vdpau-driver 0.7.4-8
VDPAU backend for VA API (32-bit)
local/lib32-mesa 1:24.2.8-1
Open-source OpenGL drivers - 32-bit
local/libva 2.22.0-1
Video Acceleration (VA) API for Linux
local/libva-intel-driver 2.4.1-3
VA-API implementation for Intel G45 and HD Graphics family
local/libva-nvidia-driver 0.0.13-1
VA-API implementation that uses NVDEC as a backend
local/mesa 1:24.2.8-1
Open-source OpenGL drivers
I may perform a test on a clean install of Manjaro later. Flatpak version of steam works fine.
Flatpak version of steam works fine.
I suspect that's because it fails to find any hardware decoder to begin with, so no crash.
I'm on an AMD CPU which may be why I can't reproduce any issue. Trying to initialize VAAPI against my CPU fails cleanly (so does trying to initialize CUDA decoding against the discrete GPU actually). I start to suspect the intel libva driver - you could try to remove lib32-libva-intel-driver and see if the crashes go away.
Also - do you have H.265 enabled in your settings? Your crash looks to be happening inside VAAPI initialization, which would mean it's trying to initialize for H.264 and use your integrated AMD GPU, which may not be what you intended.
I had GPU encoding disabled completely. Enabling both did nothing.
However: I changed the recordings directory from the settings to an empty directory (with restarting steam) and it seemed to fix both Recordings & Screenshot and Big Picture view.
If I click Take Screenshot on the timeline it still crashes with segfault (11). (same in overlay and in Screenshots view)
Removing lib32-libva-intel-driver still produces same results (crashing with Take Screenshot from a recording):
steam-screenshot-crash-log.tar.gz
I had GPU encoding disabled completely. Enabling both did nothing.
Just to confirm for clarity, you are getting this crash when bringing up the details for a game that has recordings, even if you disabled 'Enable GPU hardware encoding' in the settings?
That would make sense, our code is ignoring this setting when producing thumbnails and will still try to use your crashing hardware decoder. We will fix that on our end.
Next .. based on your logs and feedback I'm leaning towards a problem with your NVidia drivers again. If you have a /usr/lib32/dri/nvidia_drv_video.so file, you could try to move it out of the way and see if the crashes still happen.
Reason is, your 32 bit vaapi check in steam-runtime-info.txt straight up crashes:
"x11/vaapi" : {
"messages" : [
"vaCreateSurfaces (va_display, VA_RT_FORMAT_YUV420, width, height, surfaces, surfaces_count, &attr, 1) failed: attribute not supported (10)",
"i386-linux-gnu-check-va-api: vdpau_video.c:325: vdpau_DestroySurfaces: Assertion `obj_surface' failed."
],
"renderer" : null,
"version" : null,
"issues" : [
"cannot-draw"
],
"exit-status" : -1,
"terminating-signal" : 6,
"terminating-signal-name" : "Aborted"
},
I think it's just the same thing happening in the steam client.
You could get a more verbose report by setting LIBVA_MESSAGING_LEVEL=2. If it is set in /etc/libva.conf you can edit it there. Or set it in an environment variable before running steam, then run Steam Runtime Diagnostics again (the libva.conf file has priority oddly enough).
Also had this error, and fixed it by deleting the recordings directory (it looks like it was around the max size)
Here's my stack trace for when it happens:
Stack trace of thread 66821:
#0 0x00000000f7e9c5eb XDisplayString (libX11.so.6 + 0x215eb)
#1 0x00000000e441fbdd __vaDriverInit_1_22 (nvidia_drv_video.so + 0xdbdd)
#2 0x00000000eb18833c vaInitialize (libva.so.2 + 0x733c)
#3 0x00000000ebceefbe n/a (libavutil.so.59 + 0x33fbe)
#4 0x00000000ebcef53f n/a (libavutil.so.59 + 0x3453f)
#5 0x00000000ebcec09c av_hwdevice_ctx_create (libavutil.so.59 + 0x3109c)
#6 0x00000000eb66a956 n/a (libvideo.so + 0x4f956)
#7 0x00000000eb66abeb n/a (libvideo.so + 0x4fbeb)
#8 0x00000000eb66c983 n/a (libvideo.so + 0x51983)
#9 0x00000000eb6989cd n/a (libvideo.so + 0x7d9cd)
[#10](/issue/ValveSoftware/steam-for-linux/10) 0x00000000eb699069 EGetFramesFromVideo (libvideo.so + 0x7e069)
[#11](/issue/ValveSoftware/steam-for-linux/11) 0x00000000eddc3924 n/a (steamui.so + 0x7f9924)
[#12](/issue/ValveSoftware/steam-for-linux/12) 0x00000000ee58d23b n/a (steamui.so + 0xfc323b)
[#13](/issue/ValveSoftware/steam-for-linux/13) 0x00000000ed58d6de _ZN16SteamThreadTools7CThread22ThreadExceptionWrapperEPv (libtier0_s.so + 0x1c6de)
[#14](/issue/ValveSoftware/steam-for-linux/14) 0x00000000ed58b49e n/a (libtier0_s.so + 0x1a49e)
[#15](/issue/ValveSoftware/steam-for-linux/15) 0x00000000ed58bd60 CatchAndWriteMiniDumpExForVoidPtrFn (libtier0_s.so + 0x1ad60)
[#16](/issue/ValveSoftware/steam-for-linux/16) 0x00000000ed58bda8 CatchAndWriteMiniDumpForVoidPtrFn (libtier0_s.so + 0x1ada8)
[#17](/issue/ValveSoftware/steam-for-linux/17) 0x00000000ed5901c2 _ZN16SteamThreadTools7CThread10ThreadProcEPv (libtier0_s.so + 0x1f1c2)
[#18](/issue/ValveSoftware/steam-for-linux/18) 0x00000000f7bfa490 n/a (libc.so.6 + 0x91490)
[#19](/issue/ValveSoftware/steam-for-linux/19) 0x00000000f7c97408 n/a (libc.so.6 + 0x12e408)
Oddly, this happens when either launching the game, or going into the options, too.
I had GPU encoding disabled completely. Enabling both did nothing.
Just to confirm for clarity, you are getting this crash when bringing up the details for a game that has recordings, even if you disabled 'Enable GPU hardware encoding' in the settings?
Yes, I performed a test by switching both settings on and off, but I don't know if I made an error in testing as making a new recordings directory right after fixed the issue. I am now unable to reproduce the error. The bug specifically was a problem in big picture mode because steam would crash before launching the game
.
I can't remember how the desktop mode behaved, if I had to scroll down to crash or... but displaying the screenshots view would crash - not anymore. I thought I had backed up a directory where the crash still happened but using that doesn't crash either...
That would make sense, our code is ignoring this setting when producing thumbnails and will still try to use your crashing hardware decoder. We will fix that on our end.
I think that could've been it. The crash still occurs in rare cases like when taking a screenshot from the recording or when the game starts cloud sync after first game launch, but the problem as described is fixed for me.
Just like @kelvie I had like 8GB of footage when the error first happened.
It also could've been HEVC setting related:
I had the GPU hardware encoding disabled from the settings. Disabling GPU encoding made the HEVC button locked (greyed out, unable to change). I assumed GPU setting took precedence over it and it disabled both. Now the HEVC switch is completely gone.
The latest beta will also avoid using the GPU for thumbnails and screenshot extraction, so if you disable 'Enable GPU hardware encoding' because your 32 bit vaapi is unstable, you should no longer be crashing.
Closing per the last comment.
Your system information
Please describe your issue in as much detail as possible:
Recently I noticed that when I was looking at Age of Empires 2 Definitive Edition in my library in desktop view, Steam client immediately crashed. It was something that started happening only recently.
The game could be launched OK using tray/taskbar menu dropdown or right clicking the game name on the list. It was going into detailed view for the game specifically that was causing the crash.
It did not happen for other games. I figured that's because AOE2DE was the only game I played sitting at my desk, while I played other games using Remote Play on my Steam Link device. Which means, no Recording was generated for games ran through Remote Play (it doesn't record in this scenario).
So it struck me - what if I disable Recording and delete all existing Recordings (there was a little over 10 GB). I did just that and guess what - the issue was gone for good!
Afterwards I turned the Recording back on, played a bit (a couple of minutes) and generated a new Recording when playing AOE2DE and guess what - the client crashed again.
My recording settings were as follows: 120 minutes, high quality, GPU hardware encoding ON, HEVC/H.265 OFF, max frame rate 60, maximum vid height - no limit, no microphone.
So I turned off GPU hardware encoding. This time I also generated a couple minutes of recording and the issue was gone.
Oddly enough, the problem was not even with the recording itself. It clearly happened when the client was trying to show me the latest recording in the detailed view for AOE2DE.
For now I just turned it off.
Steps for reproducing this issue: