csgo crash with new steam overlay

[dreamyukii]

Your system information

• System information from steam (Steam -> Help -> System Information) in a gist:
  hardware specification
• Have you checked for system updates?: [Yes/No]

i don't know if i should report this issue at steam-for-linux or csgo-osx-linux repo

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. Please link any large pastes as a Github Gist.

Steps for reproducing this issue:

1. opt-in to steam beta
2. launch csgo
3. shift + tab
4. crash

[daxcore]

it is crashing at all: wayland + vulkan and the ToGL variant.

[learning-thing]

Also crashing for me on Arch linux, X11 KDE with nvidia GPU.
Steam Overlay use to work for me in all games, tried warframe (Proton) and Portal 2 (Native), only CSGO crashes
for me when trying to open the steam overlay.

[af7567]

Same problem here. X11, openbox, nvidia drivers, steam beta.
Overlay crashes csgo but works OK in other games.

[wojgie]

same problem, X11. however it works fine in windowed mode.

[wojgie]

this is weird, it crashed and now its working.

the game is still running in fullscreen.

[af7567]

For me it crashes in fullscreen, windowed and windowed fullscreen. Safest to just disable the overlay for now so I don't accidentally open it :)

[wojgie]

this is weird, it crashed and now its working. the game is still running in fullscreen.

alright, this is very weird. it again stopped working. i can't reproduce the issue consistently. cheers

[Douile]

Crash stacktrace on arch X11

Thread 1 "csgo_linux64" received signal SIGBUS, Bus error.
0x00007ffff7f4e772 in ?? () from /home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
(gdb) i s
#0  0x00007ffff7f4e772 in ?? () from /home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
#1  0x00007ffff7f40dd5 in ?? () from /home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
#2  0x00007ffff7f4a994 in ?? () from /home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
#3  0x00007ffff7f4b152 in ?? () from /home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
#4  0x00007ffff7f4ca6b in ?? () from /home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
#5  0x00007ffff7f3d115 in glXSwapBuffers () from /home/user/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
#6  0x00007ffff42ea803 in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/libSDL2-2.0.so.0
#7  0x00007ffff563fbb3 in ?? () from bin/linux64/launcher_client.so
#8  0x00007ffff463b0c5 in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/libtogl_client.so
#9  0x00007ffff462d194 in IDirect3DDevice9::Present(_RECT const*, _RECT const*, void*, RGNDATA const*) ()
   from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/libtogl_client.so
#10 0x00007fffde25c370 in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/shaderapidx9_client.so
#11 0x00007fffe4476c3b in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/materialsystem_client.so
#12 0x00007fffe94815cf in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/engine_client.so
#13 0x00007fffe953339b in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/engine_client.so
#14 0x00007fffe9680f98 in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/engine_client.so
#15 0x00007fffe968343c in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/engine_client.so
#16 0x00007fffe9690927 in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/engine_client.so
#17 0x00007fffe9690da4 in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/engine_client.so
#18 0x00007fffe9719f3a in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/engine_client.so
#19 0x00007fffe9713bb2 in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/engine_client.so
#20 0x00007fffe9713cd3 in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/engine_client.so
#21 0x00007fffe9945be9 in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/engine_client.so
#22 0x00007fffe971612c in ?? () from /home/user/.local/share/Steam/steamapps/common/Counter-Strike Global Offensive/bin/linux64/engine_client.so
#23 0x00007ffff563cc69 in ?? () from bin/linux64/launcher_client.so
#24 0x00007ffff563cc69 in ?? () from bin/linux64/launcher_client.so
#25 0x00007ffff5611b31 in LauncherMain () from bin/linux64/launcher_client.so
#26 0x00007ffff763c790 in __libc_start_call_main (main=main@entry=0x400650 <main>, argc=argc@entry=16, argv=argv@entry=0x7fffffffc4a8) at ../sysdeps/nptl/libc_start_call_main.h:58
#27 0x00007ffff763c84a in __libc_start_main_impl (main=0x400650 <main>, argc=16, argv=0x7fffffffc4a8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffc498)
    at ../csu/libc-start.c:360
#28 0x00000000004006fd in _start ()

[ipaqmaster]

I also experience this on XFCE4 (X11) with my PC. It has a 3900X CPU and Nvidia 2080Ti.

Was running:

• nvidia/525.89.02 (DKMS)
• Kernel 6.2.12.arch1-1

Tried full system upgrade to below but still occurs:

• nvidia/530.41.03 (DKMS)
• Kernel 6.2.13-arch1-1

Notes:

• My CS;GO runs fullscreen
• Game launch args include: gamemoderun %command% -trusted -tickrate 128 -cl_cmdrate 128 -cl_updaterate 128 -novid +mat_disable_fancy_blending +cl_forcepreload
• Game launch is preceded by a launch script which starts OBS and its NVENC replay buffer but also calls nvidia-settings -a "DigitalVibrance=716" and waits for the game to exit before returning it to 0
• Coredump reads exactly like Douile's with csgo_linux64 getting taken out by the segmentation fault kill signal while
  blaming gameoverlayrenderer.so.

For the time being have opted out of Beta. Old overlay still works fine.

---

E: For the first time in maybe a decade I got kicked for "You cannot play on secure servers" during a competitive match. No configuration change from my previous matches this evening (My team even finished with a win but I deranked not being able to rejoin 💀) 30 minutes later after trying and failing everything I could think of - I was able to join secure servers again, tested by joining dust2 official casual. What a heart attack.

[Weirdo1312]

same issue here amd+wayland+opengl crashes
however vulkan works just fine

[Fesiug]

Same. Arch Linux, X11, KDE Plasma, OpenGL, up to date.

[sparkie3]

Here on fedora 37. It crashes specifically when I Shift + Tab in game. Every time. Windowed or full screen has no effect.

[ipaqmaster]

Opted back into beta and added -vulkan to my many CS;GO custom launch options. Shift+Tabbing no longer crashes it with Vulkan rendering enabled.

[kaythomas0]

Opted back into beta and added -vulkan to my many CS;GO custom launch options. Shift+Tabbing no longer crashes it with Vulkan rendering enabled.

this fixed the issue for me on Gentoo X11, thanks

[af7567]

Adding -vulkan prevents the overlay crash for me too.
Unfortunately the game is unplayable in vulkan mode though :) it keeps freezing like it is loading textures or something.

[kisak-valve]

SIGBUS when opening the beta in-game overlay

Issue transferred from ValveSoftware/steam-for-linux#9461.
@Ryhon0 posted on 2023-05-05T07:59:57:

Your system information

• Steam client version: 1683253302
• Distribution: Arch Linux
• Opted into Steam client beta?: Yes
• Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

Opening the in-game overlay in any way crashes the game with SIGBUS. Happens on the Flatpak version, steam and steam-native-runtime from Arch repos.

coredumpctl gives the following stack trace:

#0  0x00007f6ed0243772 n/a (/home/ryhon/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so + 0x27772)

Steps for reproducing this issue:

1. Opt into the client beta
2. Launch any game
3. Open the in-game overlay using the key shortcut or by opening a link in a game

---

@kisak-valve commented on 2023-05-05T12:58:16:

Hello @Ryhon0, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. Also, please list some games you saw this issue with.

---

@Ryhon0 commented on 2023-05-05T13:42:41:

System information: https://gist.githubusercontent.com/Ryhon0/ecf1954fe4320e5050fba24a448df75e/raw/9f036b339787ca33b879e3eb98f4a967c0d65433/gistfile1.txt

This only happens with the native version of CS:GO for me.
x86 native version of GMod, Chronicles of Myrtana: Archolos and Aim Lab with Proton Experimental all work fine

[TTimo]

Please provide uploaded minidump crash IDs if you have them. Although I'm hoping we'll be able to reproduce locally.

[af7567]

I just made it crash a couple of times now, but the upload was discarded for both. The latest one with a crash ID is:

Wed May 3 22:30:00 2023 GMT: file ''/tmp/dumps/crash_20230503232958_2.dmp'', upload yes: ''CrashID=bp-ff34a97c-4327-46ef-8edf-1a6f92230503''

[upbox-org]

i've found out that changing X11 display configuration fixes this bug. EVEN after i restart CS:GO.

What did you change in detail?

[naturwundR]

Same issues on arch , X11 KDE, nvidia GPU. up2date system and client beta.

No crashes after switching the refresh rates. ( From 165hz to 144hz and back)

edit: only worked once. now again these crashes when opening the overlay.
Stack trace of thread 9681: #0 0x00007f5d6ccc8772 n/a (/home/naturwunder/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so + 0x27772) ELF object binary architecture: AMD x86-64

[PC-Heini]

I have the same issue on Fedora 38, using Wayland and a AMD RX6600.

[TTimo]

@naturwundR @PC-Heini are you using Steam beta client can you confirm that you are seeing a crash with 1683944175 or newer? (please provide updated CrashIDs)

[PC-Heini]

@TTimo, that is the exact version of the Steam client I am using. After reading comments above I also tried running CS with -vulkan. That does fix the crashing issue and the new Steam overlay works great. While it gives me more FPS, the game still feels much worse because it introduces huge lagspikes that I do not have without -vulkan.

My Steam client output while starting and crashing the game with the overlay:
https://pastebin.com/8VfRdEbF

The crashdump file it mentiones:
https://we.tl/t-NEx6bjSMQV

(Sorry if that is not the CrashID you asked for, I am new to this)

[wojgie]

I am actually having MORE issues as of recent. Using -vulkan with my normal launch options, when I go to buy keys for cases it will actually mess up my whole Steam install. I've been getting "Controller updates" and "Audio updates" and then it'll pop up a new window instance of Steam on the store page on the overlay. After of which, it will open some weird window, such as the one with my configurable hard drive with games, and often remove the additional hard drive from the list of game locations. Additionally, one interesting feature is the "PUBLIC RELEASE BUILD" visible in the top right corner of the Steam window that pops up, which isn't present on the normal instance of the application. Valve, please fix.

this is literally this issue: ValveSoftware/steam-for-linux#9795

[kaiwasaki]

I am having the same issue in csgo only. I disabled csgo overlay for now. When using -vulkan the overlay works but I get microstutters ingame.

Steam System Information

I wonder wonder why this is going on for a while now, isn't the Steam Deck also affectedd by this? If not, what is different there? Did somebody try SteamOS?

[turrini]

How I made it work: When opening STEAM, I click to launch CSGO and immediately "hold" the STEAM window as if I were going to move it until the background turns black and/or the game starts. After that, I release it, click on the game screen, and press Alt+TAB, and I see that the overlay started successfully. Apparently, there is an issue with the overlay that doesn't properly detect the environment (maybe when switcheroo happens?) and prevents it from functioning, causing a crash when triggered with Shift-TAB. In my case, doing this works every time. Watch the attached video for reference.

vokoscreen-2023-08-05_19-29-19.mp4

[wojgie]

How I made it work: When opening STEAM, I click to launch CSGO and immediately "hold" the STEAM window as if I were going to move it until the background turns black and/or the game starts. After that, I release it, click on the game screen, and press Alt+TAB, and I see that the overlay started successfully. Apparently, there is an issue with the overlay that doesn't properly detect the display and prevents it from functioning, causing a crash when triggered with Shift-TAB. In my case, doing this works every time. Watch the attached video for reference.
vokoscreen-2023-08-05_19-29-19.mp4

wow, it really seems to work

[hogcycle]

+1 for that working, that's really strange.

[Sarthak001]

+1 the above solution is working.

[af7567]

I have tried the drag while loading workaround a few times (each time someone posted a +1 here :) ) and still haven't got it to work.

[Sarthak001]

I have tried the drag while loading workaround a few times (each time someone posted a +1 here :) ) and still haven't got it to work.

You can do one thing. Copy the below settings

Restart steam
Clear in game overly data

Then try the above method.

It worked for me thrice.. :)

[af7567]

Thanks @Sarthak001 , I tried using your settings (by opting out of the beta and disabling hardware video) but it didn't work still.

What did work though is using KDE instead of openbox+xfce-panel.
I noticed in the video above that the taskbar/panel at the bottom of the screen stays visible until alt-tabbing, but that wasn't happening for me in openbox (with and without sloppy focus). csgo was taking full focus as soon as it started.

In KDE the taskbar stays "on top of" the csgo window if you are dragging another window at the time - it doesn't have to be the steam window.

It looks like this prevents csgo from taking focus at startup and for some strange reason this means the overlay can inject itself when csgo does gain focus for the first time.

If you leave the csgo window unfocused with the taskbar visible you can see the the fps of the main menu is lower until you click somewhere in csgo.

edit: While playing around in openbox I noticed that csgo starts up with a window size of 640x480 before changing to the real resolution. Could the overlay be using this as its resolution which is why it crashes after csgo has switched to 1920x1080? And delaying the focus switch to the csgo window also means delaying the overlay initialization until after csgo has switched to 1920x1080.

[hogcycle]

I'm on GNOME, not KDE. Maybe that's why?

[choskyo]

Seems related: I'd had the overlay turned off for weeks already because of the crashes when I opened it out of habit, but as of a couple of days ago the game stopped even launching, switching (hopefully temporarily) from i3 to KDE has fixed it, didn't have to add any launch options or do any dragging on open.

[markjanes-intel]

For intel platforms, disabling the mesa shader cache prevents the crash, but it may be due to changes in timing.

https://gitlab.freedesktop.org/mesa/mesa/-/issues/9597#note_2063395

[jonasmockevicius]

i started facing same issue once ive started messing with my nvidia drivers, previously never had this issue, but once i updated my drivers it stated for me. just throwing that in maybe someone can test that theory as well

[albuquerquejp]

How I made it work: When opening STEAM, I click to launch CSGO and immediately "hold" the STEAM window as if I were going to move it until the background turns black and/or the game starts. After that, I release it, click on the game screen, and press Alt+TAB, and I see that the overlay started successfully. Apparently, there is an issue with the overlay that doesn't properly detect the environment (maybe when switcheroo happens?) and prevents it from functioning, causing a crash when triggered with Shift-TAB. In my case, doing this works every time. Watch the attached video for reference.

vokoscreen-2023-08-05_19-29-19.mp4

What a strange way to fix the problem haha, but it is working!

[pohmelie]

@albuquerquejp it is not a fix, it is a workaround.

[jvik]

How I made it work: When opening STEAM, I click to launch CSGO and immediately "hold" the STEAM window as if I were going to move it until the background turns black and/or the game starts. After that, I release it, click on the game screen, and press Alt+TAB, and I see that the overlay started successfully. Apparently, there is an issue with the overlay that doesn't properly detect the environment (maybe when switcheroo happens?) and prevents it from functioning, causing a crash when triggered with Shift-TAB. In my case, doing this works every time. Watch the attached video for reference.

vokoscreen-2023-08-05_19-29-19.mp4

Can confirm. Works for me as well.

[orithecapper]

hey I managed to fix it

I had two nvidia drivers installed at the same time

mhwd remove nvidia... etcetc

[wojgie]

fixed in CS2. Issue can be closed @kisak-valve

[af7567]

No crash for me with CS2 and steam client beta 1695679261. I opened the overlay a few times and took a couple of screenshots.
Only problem is that when checking a player profile it opens google instead, but that's a different issue.

[af7567]

I managed to get it to crash today with SIGBUS again, but a different location to before and only when CS2 was only drawing one frame every 2 seconds.

Crash reason:  SIGBUS
Crash address: 0x7f6097fff830

Thread 22 (crashed)
 0  gameoverlayrenderer.so + 0x37482
    rax = 0x0000000000000000   rdx = 0x0000000000000000
    rcx = 0x00007f6217157350   rbx = 0x00007f6181bfb540
    rsi = 0x0000000000000000   rdi = 0x00007f6097fff830
    rbp = 0x00000000004b9600   rsp = 0x00007f61a7dfd418
     r8 = 0x00007f6180000048    r9 = 0x00007f61800008e0
    r10 = 0x00007f6180ee7780   r11 = 0x0000000000000013
    r12 = 0x00000000038b0800   r13 = 0x0000000000000a91
    r14 = 0x00007f6097fff830   r15 = 0x00000000000005a0
    rip = 0x00007f621713e482
    Found by: given as instruction pointer in context

No CrashID because

Thu Sep 28 12:43:32 2023 GMT: file ''/tmp/dumps/crash_20230928134330_2.dmp'', upload no: ''HTTP response code said error''

I can reproduce the crash by starting CS2 and going to "Watch matches and tournaments".
Download a match, and then choose to "Watch this round" so it should load the round you want.
While it loads very slowly, spam shift-tab until it crashes.

If I click the watch button to watch the demo from the start it loads normally, only the watch this round option seems to have a problem.

[tyqualters]

Replying to #3172 (comment)

I don’t think this is isolated to this incident, I’ve gotten crashes too from when I Shift-Tabbed during resource intensive loading.

However, it’s fairly uncommon and I don’t have any specific details.

[wojgie]

the crashes also happen on windows, and in other games. this issue is fixed

[kisak-valve]

Now that it's harder to encounter this issue with Counter Strike, it's fairly clear that this is the same issue as ValveSoftware/steam-for-linux#9586. Closing in favor of the other issue report.