Summary
Every Chromium zygote process crashes with SIGSEGV inside Steam's overlay library gameoverlayrenderer.so (~/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so) whenever Steam is running. The crash happens during Steam's loader-time init of the overlay, which is injected into the browser via LD_PRELOAD.
This is distinct from the known overlay crashes inside games (e.g. #10164, #9461) — here the overlay crashes a non-Steam Chromium process on load, not a game.
Environment
- OS: Omarchy (Arch-based) / kernel 7.2.0-1-cachyos
- Session: Wayland (Hyprland)
- GPU: AMD RX 9060 XT (Navi 44), mesa 3:26.2.1-1
- chrome:
chromium 151.0.7922.173-1.1
- steam:
steam 1.0.0.87-3
gameoverlayrenderer.so mtime: 2026-08-03 17:46
Reproduction
- Run Steam.
- Launch any game so the overlay is active (observed with appid 268910).
- Close the game.
- Chromium's zygote segfaults on restart / while Steam is running.
Observed repeatedly: Aug 27 20:10, 20:17, 20:22, Aug 28 00:28 (4 identical crashes in the same session).
coredumpctl info (PID 127590)
Signal: 11 (SEGV) si_code: SEGV_MAPERR
Command Line: /usr/lib/chromium/chromium --type=zygote --no-zygote-sandbox --crashpad-handler-pid=127580 --enable-crash-reporter= --change-stack-guard-on-fork=enable
#0 gameoverlayrenderer.so + 0x32bc3
#1 gameoverlayrenderer.so + 0x32f49
#2 gameoverlayrenderer.so + 0x3bb4b
#3 gameoverlayrenderer.so + 0x4e311
#4 ld-linux-x86-64.so.2 + 0x61ef
#5 ld-linux-x86-64.so.2 + 0x62cd
#6 ld-linux-x86-64.so.2 + 0x218c0
All crash cores show the same top frame (gameoverlayrenderer.so + 0x32bc3); the overlay faults during its initializer invoked from the dynamic linker (frames in ld-linux-x86-64.so.2 under the overlay init).
No OOM involved (memory available, no OOM-kill in the journal).
Expected
Chromium zygote should not crash when Steam's overlay is loaded into it.
Impact
Low severity but noisy: repeated SEGV core dumps and Chromium zygote restarts while Steam is open. Workaround: disabling the Steam in-game overlay (or running the browser without Steam) avoids it.
Filed by big-pickle via opencode.
Summary
Every Chromium zygote process crashes with
SIGSEGVinside Steam's overlay librarygameoverlayrenderer.so(~/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so) whenever Steam is running. The crash happens during Steam's loader-time init of the overlay, which is injected into the browser viaLD_PRELOAD.This is distinct from the known overlay crashes inside games (e.g. #10164, #9461) — here the overlay crashes a non-Steam Chromium process on load, not a game.
Environment
chromium 151.0.7922.173-1.1steam 1.0.0.87-3gameoverlayrenderer.somtime: 2026-08-03 17:46Reproduction
Observed repeatedly: Aug 27 20:10, 20:17, 20:22, Aug 28 00:28 (4 identical crashes in the same session).
coredumpctl info (PID 127590)
All crash cores show the same top frame (
gameoverlayrenderer.so + 0x32bc3); the overlay faults during its initializer invoked from the dynamic linker (frames inld-linux-x86-64.so.2under the overlay init).No OOM involved (memory available, no OOM-kill in the journal).
Expected
Chromium zygote should not crash when Steam's overlay is loaded into it.
Impact
Low severity but noisy: repeated
SEGVcore dumps and Chromium zygote restarts while Steam is open. Workaround: disabling the Steam in-game overlay (or running the browser without Steam) avoids it.Filed by big-pickle via opencode.