steamwebhelper crashing on NVIDIA with GPU-accelerated web rendering (workaround in beta) #9780
Comments
|
This problem also happens on OpenSUSE Tumbleweed. Steam opens and the tray icon appears and all, but no UI. This started to happen the day a mesa downgrade happened on Tumbleweed, 7 days ago. Back then running zypper dup with --allow-vendor-change used to fix it, but now it's broken again and that does not fix it anymore. Systemd journal also seems to briefly mention a problem with libcef.so: Trying to run the steamwebhelper also errors on libcef.so: Running with -bigpicture I get the same result as you do too. However, one thing seems to work: if I open Steam's old UI instead of the new one with |
|
(( More possibly related issues: #9383 (diff: Flatpak, opt) and #9706 (diff: KDE) ))
Thanks, running However, it felt slow and attempting to change "Steam Library Folders" setting crashed the entire GUI (reloading it). 
Additionally, the "Friends Network" (chat) didn't work, and opening "Big Picture Mode" with
libraryfolders.vdf |
|
Okay yeah we surely have the same problem then! For me, the friends window on -vgui tells me I'm offline (I'm clearly not, even updating games in Steam itself work witgh -vgui). Tho I did not try to actually launch any games yet lol. Leaving my logs here too since we do have the same problem: logs.tar.gz I'm on OpenSUSE Tumbleweed, XFCE and NVidia 1070Ti |
onegentig
changed the title
|
I'm having the same issues as @nickonegen , I think we only differ in our hardware
|
|
I was able to get Steam to launch normally without |
Right, so far this (or similar) issue was see on various DEs (GNOME1 3, KDE4 6, XFCE2) and distros, (Fedora1 3 4, Ubuntu5, openSUSE2, Arch7), even on the Flatpak8 release – but all affected systems have a NVIDIA GPU in the GeForce 900 generation or younger. I haven't seen a report of someone with older GPU or a non-NVIDIA GPU have this problem. Can't speak for all distros (GPU driver version isn't shown in most issues) but at least for Fedora, I can safely say that all these GPUs use the same Perhaps the label:NVIDIA drivers could be applied to this issue? Now, I am by no means an expert in this field, but if they [can] use the same driver, their interface can't be all that different, and might be possibly the same in eyes of apps like Steam? |
While I tried this, I decided to give it another shot, and I found something. Removing However after a few attempts, not even Given how many symlinks are in that directory, I can't say I am surprised. 😅 I saved copies of the Steam directory while it worked and after it stopped working and ran it through I will continue experimenting with it, but so far, only Addendum: I've seen some people report that they at least get to the login screen – I wasn't so lucky. |
I have similar (Don't want to say "same" yet, because I have not read through all the posts carefully), issue with Arch+i3wm+amd RX6600 GPU. Ussually some variation of the following sequence gets the steam running, but it requires several tries: Edit: I've removed cinnamon and openbox DE that i had installed from the past + the dependencies installed by those packages and steam now starts normally even without the Edit2: From the pacman log |
|
Quoting someone from NVidia in some discord group: “from what I could see it looks like it might be a race condition in CEF” So it makes sense that -vgui launches, since it didn’t use CEF while the new UI is apparently made in HTML and uses CEF for everything. |
|
|
I’ve opened with -vgui and joined the beta, but the problem persists when not using -vgui for me. |
|
disregard what I said, the problem persists. It's just that if I leave the big picture looping like how @nickonegen showed at some point at random it starts normally if you leave it looping, but when you start a game it starts looping again and the game ends up being unplayable... at least -vgui works and now I can open the game options panel there, which was actually a problem until now. |
|
After joining the beta yesterday night, I booted my PC today and Steam is indeed working without -vgui lol (kinda laggy tho) |
|
not working even with the beta for me. |
|
Did a dnf update today and I'm hit with the exact same issue :( running with flatpak steam, I was able to get in with the -vgui flag but it seems to have no network connectivity. The new UI or big picture mode won't launch at all, just stuck in a loop |
|
With an RTX 3080, this was what I had to do to get steam working properly
Edit: On x11 with 535 drivers |
|
How come you have this directory there and I don't? |
Can confirm, this appears to have fixed the issue for me, at least for the time being, on a GTX 1070. |
No dice for me :( RTX 3060 on driver 535, Fedora 38 |
It fixed the problem for me too, (I skipped step 3 though) |
Apologies for the late reply, but I wanted to test things out before replying. The command And sure enough, after wiping this folder, it looks like it worked!
Steam now seems to work correctly via terminal and .desktop link. I restarted it several times to make sure, and for now, it looks like it… just works! I wonder why the folder difference – according to NVIDIA Dev-Guide, Either way, most of y’all should have it at Quick sidenote: I noticed that I was able to run all games and even the GUI through Lutris, and I couldn’t for a long time figure out what was different. Well, if the GLCache was at fault, Lutris had to do something with or around that – and it looks like it just straight up used its own cache in On the latest Beta Update (steam-runtime_0.20230509.49499), I re-enabled "GPU-accelerated web rendering", and so far it looks like it all works without problems (incl. Big Picture). According to the changelog, the issue should be patched – though it’s likely still worked on (they call it a workaround), and I kinda won’t be surprised if it broke in a few restarts (it’s beta afterall) – I’ll update this post if that happens. :) |
|
Alright I was able to get it working again by uninstalling the Flatpak version and installing the rpm-fusion package, seems to be working as normal now |
|
Mine is still broken after trying everyone's advice. I am an arch user on latest everything with a 2070 super. |
|
@Drogobo Have you tried steam-native or steam -vgui from console? |
|
I am just going to add that I was having what I believe to be this same issue with an Intel igpu and the |
|
Damn, I got a fully AMD system thus this is not exclusive to Nvidia, not even -cef-disable-gpu can make it start, I even downgraded my glibc from 2.38 to 2.37 to no avail. |
|
I also have a full AMD system and the only way I can launch steam currently is by right clicking on the icon and selecting library edit: I have also disabled friends and chat from opening on start although I have no idea if that makes any difference |
|
Fedora 38/ Full AMD user here. Originally used the |
This worked for me as well. If I start steam in the terminal, it works fine. Otherwise I get webrender errors. |
|
Hello @vaparetia, same as #9780 (comment), you've described #9383. |
|
I'm encountering this error when I don't start Steam from the terminal. Starting Steam from the terminal works fine. |
|
29/11/2023 I have the issue that steam either from the desktop or via a terminal crashes and burns offering(terminal) to upload crash dumps. Iam on Arch fully updated system. not sure how to progress. Have tried various things. Onm plasma latest under wayland steam works perfectly( unfortunately my system is not stable under wayland) |
|
Issue still exists for me. My System: Steam starts from Desktop and closes right after beeing fully startet (can shortly see the client). It spawns alot of "steamwebhelper" (more than usual). |
|
Same issue here. Fedora 38 AMD GPU Opting into beta did not fix. what did work was disabling the "Enable GPU accelerated rendering in web views" option under Interface |
This did the trick for me. system info:
|
|
I think disabling hardware accelerated web views works. Another alternative (which still keeps hardware accelerated web view) is:
This fixes for me. I'm on KDE, with AMD RX 6800 if that matters. |
This was my issue. Some further detail for anyone who comes across this as no other solutions helped since I'm fully AMD. Lately i'd been working on setting up a GPU passthrough for Windows 10 and had the discrete GPU disabled in /etc/modprobe.d/vfio.conf and using the iGPU natively on Arch. After re-enabling the discrete GPU (removing the vfio.conf file and running mkinitcpio) and plugging in my monitors back to its ports, I forgot to isolate and disable the iGPU I was previously using. Going back and repeating the process to the iGPU fixed this issue after a reboot. I had not tried running steam prior to this instance so I don't know if any other factors were at play. |
|
I have experienced this issue without hardware acceleration in web view. |
|
I seem to be experiencing this issue, albiet with an extra segfault, in WSL2 (admittedly, an uncommon use case). I'm using Ubuntu 22.04, and none of the fixes mentioned so far have worked for me (so far as I'm able to try them at least, Portion of CLI output: |
This solved the issue for me (Linux Mint Edge 21.3 / Kernel 6.5 / Ryzen 7 7700X / Sapphire Radeon 7700 XT NITRO OC 12GB Went into the BIOS, found the setting for the integrated graphics mode and set it to disabled. Steam worked immediately on reboot. Weirdly, Steam ran find from the terminal when I invoked it with |
|
Assert( Failed creating offscreen shared JS context ):/data/src/steamUI/steamuisharedjscontroller.cpp:546 These are some symptoms found during launch attempts using
|
|
For me under LMDE6 (Debian 12) it runs with the parameter "-cef-in-process-gpu" I had to try for quite a while until I found that out before it was absolutely impossible to get it to start and always hung at loading user data. |
|
@kisak-valve any chance you'll hire some of us on here to look at / address some of the issues seen on GitHub? We all have the time & passion to fix some of this, but we're excluded from helping. |
|
@KenTheWhaleGoddess Nice to hear that it works. If it does not work, deactivate the internet connection, start Steam and reactivate the internet when the client tries to log in. Apparently the problem is caused by several software bugs, no wonder with the software junk that Valve delivers. |
|
add another workaround to this issue: |
This is a workaround for the same symptom (a steamwebhelper crash) happening for a different reason, and is tracked at #10549 rather than here. |
|
@kisak-valve, perhaps you could retitle this to something like "steamwebhelper crashing on Nvidia with GPU-accelerated web rendering (workaround in beta)" to narrow down its scope? |
kisak-valve
changed the title
kisak-valve
changed the title
|
Hi Kisak, thanks for keeping track of the issues. I am on the beta version: I noticed that after I delete GLCache ( Thanks again |
|
Same or similar issue here:
Tried absolutely everything, no luck. Although I found something: |
|
I'm not sure if it's useful. |
and others
Since yesterday (1. July 2023), Steam hangs on start, unable to create a window for itself (new GUI problem?). It appears that
start.shis repeatedly trying to create asteamwebhelperthat just crashes soon after spawning.Update: Identified as a CEF (libcef.so) issue, it’s currently tracked by NVIDIA and looks like a workaround is out in Steam Beta (see changelog). Should be fixed by disabling "GPU-accelerated web rendering" and wiping GLCache, see #9780 (comment).
System Information
$ dnf list installed "*steam*"$ dnf list installed "*nvidia*"$ inxi -FDescription
When I try to start Steam either from the terminal or from the application launcher, the process just hangs and doesn't open the Steam client (has to be killed using
killor justkillall steam).The issue started appeared one day ago–Steam was working perfectly fine before that. I made no changes to the system, settings or anything in that time (auto-update might have happened though).
Executing
steamin the terminal didn't print any errors or any lines that would differ from a successful launch. After "RegisterForAppOverview", it appears thatsteamwebhelperwas repeatedly executed:The longer I let it run, the more
steamwebhelpers were spawned (seen inhtopandps aux | grep 'steam', no window ever appeared. At this point, the program didn't respond to even SIGINTs and had to be forcibly killed.By some miracle, I was able to start Steam in offline mode (
steam -offline) once after runningsteam --reset. Games, incl. online ones, ran as expected. But sadly, after I restarted the computer again, not even the offline option helped (I tried resetting again, no change).Addendum: Running
steam -bigpicturefails in a…peculiar way (video)Screencast.from.2023-07-03.00-08-47.webm
Steps for reproducing this issue:
What I tried so far:
steam -offlinesteam --resetsteam --flushconfigsteam -cef-disable-gpusteam -bigpictureDRI_PRIME=0 steamdnf downgrade steamdnf reinstall steamdnf remove steam && dnf install steamrm -rf ~/.cache/nvidia/GLCacherm -rf ~/.steam/ ~/.steampath ~/.steampidrm -rf ~/.local/share/Steam/(worked for a time, see #9780 (comment))steam -vgui(works to a limited extent, see #9780 (comment))The text was updated successfully, but these errors were encountered: