Closed sizeofbool closed 6 years ago
Confirmed on Arch Linux x86_64 with i3wm & proprietary nvidia drivers, steam runtime disabled, so not only Debian.
same here, gentoo amd64, open drivers (VIDEO_CARDS="amdgpu radeonsi radeon" in make.conf), latest updates make steam overlay freeze the game (not always) ask for debug info with specific commands, i'll post all i can
@kisak-valve @Plagman I have caught this bug once again and managed to create core-dump file of frozen "gameoverlayui" process with gdb before killing it with main game process. I can send you this core-dump file to debug, but I need secure way to do this. File is ~24Mb big 7-zip archive. If you need any additional assistance, just ask, I'll be happy to help.
Same for me while playing CSGO. When overlay is open and CSGO tries to go to next match, it freezes.
Can confirm, this happened to me while streaming Salt and Sanctuary live just now. I am on the May 23rd Client Beta.
Computer Information:
Manufacturer: Unknown
Model: Unknown
Form Factor: Desktop
No Touch Input Detected
Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD FX-8370E Eight-Core Processor
CPU Family: 0x15
CPU Model: 0x2
CPU Stepping: 0x0
CPU Type: 0x0
Speed: 4214 Mhz
8 logical processors
8 physical processors
HyperThreading: Unsupported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
Network Information:
Network Speed:
Operating System Version:
Ubuntu MATE 16.04.2 LTS (64 bit)
Kernel Name: Linux
Kernel Version: 4.10.0-16.1-liquorix-amd64
X Server Vendor: The X.Org Foundation
X Server Release: 11804000
X Window Manager: KWin
Steam Runtime Version: steam-runtime-beta-release_2016-12-05
Video Card:
Driver: NVIDIA Corporation GeForce GTX 1080/PCIe/SSE2
Driver Version: 4.5.0 NVIDIA 381.22
OpenGL Version: 4.5
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 60 Hz
VendorID: 0x10de
DeviceID: 0x1b80
Revision Not Detected
Number of Monitors: 2
Number of Logical Video Cards: 1
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 3840 x 1080
Primary Display Size: 20,08" x 11,42" (23,07" diag)
51,0cm x 29,0cm (58,6cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 8192 MB
Supported MSAA Modes: 2x 4x 8x 16x
Sound card:
Audio device: Realtek ALC892
Memory:
RAM: 15726 Mb
Miscellaneous:
UI Language: English
LANG: pt_PT.UTF-8
Microphone: Not set
Steam Controller Cable and Base: Not set
Total Hard Disk Space Available: 469085 Mb
Largest Free Hard Disk Block: 169433 Mb
VR Headset: None detected
Recent Failure Reports:
This is still a problem, and a quite urgent one too. The overlay is a major part of the Steam Experience, and not being able to use it is really annoying, especially for trading - I used to trade tf2 items sometimes, but now I can't because trading with someone from the current server (i.e. on trading servers) requires use of the overlay, which freezes my game.
Valve, pls fix
It doesn't happen very often to me, but if it freezes, then after a while both the game and Steam client crash.
@kisak-valve @Plagman I'm still experiencing freezes of Steam In-Game Overlay. This time in game Starbound. I've retraced my actions:
Steam Client Beta package version: 1497895186 (Built: Jun 16 2017, at 23:28:55)
This happens to me as well. Such a severe issue like this should demand priority. Please, if you need any more information for this just ask. I'm more than willing to help fix something that kills my gaming experience like this.
My system information https://gist.github.com/ElectricTriangle/96eab8d9837e338afa404351b656be9c
I get this also; exact same symptoms as described by everyone above. It seems to happen pretty often in my case. I'll update this post if I find a reliable way to reproduce it.
I'm running Ubuntu 16.04 and 17.04, with Gnome 3, for reference.
This is a really serious bug that I also hope will be made a priority.
Same here Linux Mint 18.1 x64 Mate Edition GPU-Driver: xserver-xorg-video-nouveau GPU: Nvidia GF 710M Game Mount & Blade: Warband
It's a distro-agnostic issue affecting all sorts of graphics cards, including my Intel HD Graphics 5500. Same symptoms as the others.
Same here, Debian 8 Jessie, gnome-shell, gtx980 nvidia drivers
I'm also getting this problem on Ubuntu Mate 16.04.2 LTS, Linux 4.4 and nvidia gtx970. It happens in all games and it happens every single time, it takes about a minute of using the overlay or by taking more than 1 screenshot. This problem has been present for months, many months earlier than this bug was posted here, so I hope it is given the importance it deserves. The game becomes completely inaccessible when this happens by the way.
yes it's a regression, until few months ago screenshots used to work perfectly and consistently (in most games except few UE4 ones like Ark and Hatred)
Game: L4D2 OS: Debian 9.0.0 and Debian Sid GPU: GTX 660M GPU-driver: official proprietary non-free nvidia-driver Launch command: optirun %command% -novid -console
Until today: Open the steam-overlay while the red l4d2 loading-circle next to "Addons" in the mainmenu is still running.
Since today: (I did not perform any update/upgrade and didn't install or remove ANY packages since 3 days) Open the steam-overlay where ever you want (mainmanu, ingame, lobby...), wait ~6 secs.
Now the overlay is working again, without freezing.. for now.. I removed nearly all my addons, maybe that contributes to this, idk...
I get it too, on some games it takes seconds and others it happens a couple of times. Game: CS:GO, L4D2, Rust, etc. OS: Debian 9.0 Stretch GPU: GTX 750 Ti GPU-driver: NVIDIA version 375.66 (proprietary, tested)
The only way I found to fix it without killing the game is to open a system process manager tool, stop the game, kill the gameoverlayui process, and then continue the game. It basically just kills the game overlay altogether, but you can still continue playing.
Thanks, but I can't use this fix, because the frozen overlay is in front of everything, even the system process manager tool.
And i switched to the console screen (STRG+ALT+F1) and killed the overlay process with HTOP, but there is no change. only killing the user or restarting the computer are helping. :(
@MartinX3 You might need to kill it with SIGKILL, it's signal handler might be hanging.
@Majora320 First thank you for your help :) But I already tried it :( The process got killed but my system was still frozen on the xserver screen. :( But I tested it only on my Linux Mint 18.2 x64 Mate-Desktop. :)
Ubuntu 17.04 problem persists
Still a thing on Debian. Quite annoying in combination with games that do not save, I must say.. .
I have the same problem with KDE Neon. I also notice some weird bug which makes me suddenly move around a bit in CS:GO. Like using TAB when standing still turns me around, dunno if its related, probably not but I guess it happened at the same time. Quite annoying and also XP lost.
I have crashes when using the overlay too. Steam beta, nvidia 384.69 (and other versions), slackware64-current, Tried with i3wm and openbox. Just opening the overlay and using the friends list and chat seems OK, but opening the in game web browser (or viewing player profiles) usually causes a crash after a few seconds and the only way to fix it is to kill -9 the game.
#0 0x00007f03c60ab829 in syscall () from /lib64/libc.so.6
#1 0x00007f03c67dcd8b in ?? () from /home/adamf/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
#2 0x00007f03c67dd00a in ?? () from /home/adamf/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
#3 0x00007f03c67e30d1 in ?? () from /home/adamf/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
#4 0x00007f03c67e3374 in ?? () from /home/adamf/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
#5 0x00007f03c67eb929 in ?? () from /home/adamf/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
#6 0x00007f03c67ed585 in ?? () from /home/adamf/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
#7 0x00007f03c67e79ee in glXSwapBuffers () from /home/adamf/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so
#8 0x00007f03c2c01c22 in ?? ()
edit: While trying to find more info I have found a "fix". When the overlay crashes I can run
strace -p `pidof csgo_linux64`
and then when CTRL-C'ing strace, csgo is working again :)
edit2: Sending these 2 signals seems to be the best way to unfreeze csgo, I guess it should work for other games too.
killall -STOP csgo_linux64
killall -CONT csgo_linux64
@Plagman @kisak-valve can you please give a status update on this issue? It seems to affect a very large range of distros and graphics cards and is a top-priority critical bug that completely ruins trading. It has been about 5 months (!) since this issue was first reported, with no visible progress being made on it despite its severity.
I just had the overlay freeze today when only using chat, so doesn't look like it is caused by the in game web browser.
Unrelated but I seem to get the same issue on the windows version. Any steam overlay windows will freeze the whole system for 15s since last steam update
@Citillara Not the same issue - on Linux, the freeze isn't just 15s but until you kill the process. You should open a new issue.
Hello @Citillara, it probably would be better to reach out to Steam Support with your issue.
@kisak-valve Can you please, as I said above, give a status update on the fix? Because it sounds to me like you're giving a Windows issue first priority while ignoring for months a much more serious Linux issue.
@Majora320, friendly reminder that I'm a moderator for the Valve issue trackers. I don't have more insight into this particular issue than you do and we'll need to wait to hear back from a Steam dev.
Since windows-only issues are not tracked here, those issues should either go to the forums or Steam Support.
Sorry for getting annoyed at you specifically, I know you're not a Steam dev. But this is a perfect example of why I don't like closed-source software. Not only is the community unable to fix anything, the company can feel free to ignore any nontrivial bugs just because they occur on a platform with a relatively small percentage of its userbase. Steam devs - If you can't reproduce this issue, etc. I'd be happy to help. You can remote access my desktop if you really want to. I just want this bug fixed so I can actually trade items, which is a big part of the TF2 (at least) ecosystem. And this no-feedback thing is fully representative of Valve as a whole now.
5 months with no feedback is a hell of a long time. I think I'm going to be buying more games from GOG in the future.
Yes, we've been unable to ever reproduce the issue; it seems to be a very specific interaction problem. Using your remote setup would not be especially useful, but one thing you could try is to capture a core dump of both gameoverlayui and the game process when it's in that frozen state, since it's easy for you to reproduce. Making them crash by hand (with kill -11) might even be enough to generate a Minidump through our system, if you can send us these files after.
@Plagman Would you mind giving me your gpg pubkey so I can send you the dump encrypted? I got TF2 to crash in the trading ui after a little while. Ran kill -11 gameoverlayui
which generated a steam coredump (which was, apparently, discarded, though I have the files saved). When I ran kill -11 hl2_linux
, the game resumed normally (?).
I just got it to freeze while using the overlay on csgo and forced a core dump using gdb, the coredump for csgo is 2.6GB though so a bit too big to upload. I also killed the 2 processes with signal 11 which created minidumps so I have attached them. csgo_overlaycrash.zip
Both csgo_linux64 and gameoverlayui were stuck in libc
csgo_linux64: (the same as the bt in my comment above)
gameoverlayui:
My libc version is glibc-2.26 on slackware64 multilib.
This bug is still not fixed. CSGO freezes if overlay is opened for a few seconds. Affecting Arch Linux in my case.
Yes buying cs:go skins / keys using the market in the overlay browser is almost impossible, last time I tried I had to kill and restart the game like 5 times to buy one. I tried to use Firefox but it sucks because you can't see the skin in-game.
It's unfortunate because throwing money on pretty skins was somehow relaxing and pleasing for my mood (I guess like buying shoes for ladies), so I'm currently stressed, sad and with money sitting in my wallet.
Debian 8.9 in my case so I guess it affects also SteamOS.
I have created a little script in my $PATH called csgo.sh which contains
#!/bin/bash
killall -STOP csgo_linux64
killall -CONT csgo_linux64
Whenever I am using the overlay in csgo and it freezes I just have to press WIN+R (since I have a shortcut which runs dmenu_run) and type csgo, press enter, and it's OK again for a few more seconds.
It's just a hack, but it is working OK for me at the moment.
Any news about this? It's quite annoying.
I have also some problems when showing the score, when pressing
While I confirm that the killall trick works (thanks for that), the freezing in cs:go actually got worst: more or less after the 'new dust 2' update, it's now pretty impossible to check a user profile, the browser will freeze both itself and the game in like 2 seconds. Good bye buying skins.
Problem persists on Ubuntu 17.04 x64. Just a note - I can still hear sound in game. I'm glad we have a trick to solve it now, but it's annoying to the point I have just disabled steam overlay.
Ubuntu 17.10 x64 too
Same problem (payday 2, cs:go)
I'm having the same issue on Arch linux with both stable and beta client of steam. I would really really appreciate a fix for this.
Same here. Occurs in every game I have... It's quite frustrating especialy that there is no way to turn off achivement and "new item" notifications...
Steam: Version 1513371133 / Compilation Dec 15 2017 (11:47:57) / Steam API: v017 OS: Ubuntu 16.04 / 4.4.0-112 x64 / Unity Hardware: Lenovo X220 / Intel i5 2520M / 8GB RAM
What percentage of Linux users can we assume are affected? It's been affecting me now for around a month now, and it doesn't seem like there's been much progress here.
DE: MATE with compiz. Running Steam on Ubuntu 16.04 64-bit. Built Jan 25, 2018. API: v018 steam-runtime-beta-release_2017-10-05 CPU Brand: Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz Driver: NVIDIA Corporation GeForce GTX 780M/PCIe/SSE2
@DarkAceZ This problem has almost been around for a year now, but I'm not sure we know exactly what's causing it. It would be nice to get an update from @kisak-valve if there's any progress or anything we can do to help.
A race condition is most likely the cause for this problem. Overlay process or game process are waiting for some condition to appear, because you can escape from this state by these steps:
I have found that I only need to pause and continue the game process and then the overlay continues to work as normal (until the next time it freezes).
Hello @mlandalv, just so that it's clear, I'm a moderator on these issue trackers, not a Valve dev.
We'll need to wait to hear from a Steam dev for any updates on this issue.
My system information
CPU: Intel i5-6600 MEM: 16Gb VGA: nVidia GTX1060 6Gb (proprietary driver 375.39) OS: Debian GNU/Linux 9.0
stretch
x86_64 (Kernel Debian 4.9.18-1 (2017-03-30)) DE: Xfce 4.12 (lightdm + xfwm4), default settings, compositor enabled. X11: X.Org version 1.19.2Please describe your issue in as much detail as possible:
Sometimes, when I open Steam In-Game Overlay in Left 4 Dead 2 or in other game, game could freeze and overlay stops responding. When this happens I still can Alt+Tab to other opened windows, such as Steam Client main window and chat windows, access my desktop, etc, but game stays frozen and the only way to close it is by kill command. Frozen game process uses almost no CPU power. Steam Client log
Steps for reproducing this issue:
There is no reliable way to reproduce this issue, but I've noticed it happens more often when I open overlay too soon while overlay still loading (message about accessing overlay in game wasn't displayed yet). Sometimes it happens mid-game while I've accessed overlay multiple times before without any problems. Game and overlay freezes only when I open overlay. (Game runs normally if I don't open overlay)