protonscr

Consistent Steamwebhelper crashing on NVIDIA 470 series driver

steamopen Distro Family: DebianWeb Component
ValveSoftware/steam-for-linux#10599 · opened 2024-03-09 by Chaussettes99 · updated 2024-03-12 · 10 comments · github
CChaussettes99 2024-03-09 github

Your system information

  • Steam client version (build number or date): Wed, Mar 6 3:28 PM UTC -08:00
  • Distribution (e.g. Ubuntu): Debian 12.5 Bookworm
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Steam Logs: steam-logs.tar.gz
  • GPU: Nvidia GeForce GT 635

Please describe your issue in as much detail as possible:

Upon opening the Steam client, a window (attached below) will appear saying Steamwebhelper has stopped responding. This issue started appearing roughly last week, when all of the other issues for Steamwebhelper started appearing, which makes me believe this is not a system issue specific to me. I can still open Steam and get to the library when choosing 'Restart Steam', but it will always fail the first try after having Steam closed for a while.

I have tried opting into the Steam Client Beta and the issue still persists. I have also ensured that my /tmp/dumps directory is owned by my user account and that there are no symlinks in '~/.config/`.

Steps for reproducing this issue:

  1. Open Steam
  2. Steamwebhelper crashes

Screenshot_20240309_145429

Ssmcv 2024-03-12 github

Text from attached steamwebhelper.log, which is often the most important log for symptoms similar to this one:

steamwebhelper.sh[14636]: === Sat Mar  9 05:13:24 PM EST 2024 ===
steamwebhelper.sh[14636]: Starting steamwebhelper under bootstrap sniper steam runtime at /home/chaussettes/.steam/debian-installation/ubuntu12_64/steam-runtime-sniper
exec ./steamwebhelper --no-sandbox -lang=en_US -cachedir=/home/chaussettes/.steam/debian-installation/config/htmlcache -steampid=14615 -buildid=1709846872 -steamid=0 -logdir=/home/chaussettes/.steam/debian-installation/logs -uimode=7 -startcount=0 -steamuniverse=Public -realm=Global -clientui=/home/chaussettes/.steam/debian-installation/clientui -steampath=/home/chaussettes/.steam/debian-installation/ubuntu12_32/steam -launcher=0 -use_safe_shutdown_workaround -use_xcomposite_workaround -no-restart-on-ui-mode-change --enable-smooth-scrolling --password-store=basic --log-file=/home/chaussettes/.steam/debian-installation/logs/cef_log.txt --disable-quick-menu --disable-features=DcheckIsFatal
[0309/171423.628043:ERROR:context.cc(100)] The browser_subprocess_path directory (./steamwebhelper) is not an absolute path. Defaulting to empty.
[0309/171425.733029:WARNING:crash_reporting.cc(278)] Failed to set crash key: UserID with value: 0
[0309/171425.780964:WARNING:crash_reporting.cc(278)] Failed to set crash key: BuildID with value: 1709756822
[0309/171425.781001:WARNING:crash_reporting.cc(278)] Failed to set crash key: SteamUniverse with value: Public
[0309/171425.781026:WARNING:crash_reporting.cc(278)] Failed to set crash key: Vendor with value: Valve
[0309/171425.781053:WARNING:crash_reporting.cc(278)] Failed to set crash key: Platform with value: Linux
[0309/171426.076393:INFO:crash_reporting.cc(239)] Crash reporting enabled for process: browser
[0309/171426.379491:WARNING:task_impl.cc(32)] No task runner for threadId 0
[0309/171426.409552:WARNING:task_impl.cc(32)] No task runner for threadId 0
[0309/171426.462129:WARNING:crash_reporting.cc(278)] Failed to set crash key: UserID with value: 0
[0309/171426.462376:WARNING:crash_reporting.cc(278)] Failed to set crash key: BuildID with value: 1709846872
[0309/171426.462389:WARNING:crash_reporting.cc(278)] Failed to set crash key: SteamUniverse with value: Public
[0309/171426.462401:WARNING:crash_reporting.cc(278)] Failed to set crash key: Vendor with value: Valve
[0309/171426.462412:WARNING:crash_reporting.cc(278)] Failed to set crash key: Platform with value: Linux
[0309/171426.476790:WARNING:crash_reporting.cc(278)] Failed to set crash key: UserID with value: 0
[0309/171426.476985:WARNING:crash_reporting.cc(278)] Failed to set crash key: BuildID with value: 1709846872
[0309/171426.476997:WARNING:crash_reporting.cc(278)] Failed to set crash key: SteamUniverse with value: Public
[0309/171426.477009:WARNING:crash_reporting.cc(278)] Failed to set crash key: Vendor with value: Valve
[0309/171426.477020:WARNING:crash_reporting.cc(278)] Failed to set crash key: Platform with value: Linux
Gtk-Message: 17:15:00.925: Failed to load module "xapp-gtk3-module"
Gtk-Message: 17:15:00.939: Failed to load module "appmenu-gtk-module"
Gtk-Message: 17:15:01.575: Failed to load module "colorreload-gtk-module"
Gtk-Message: 17:15:01.576: Failed to load module "window-decorations-gtk-module"
[0309/171503.223256:INFO:crash_reporting.cc(262)] Crash reporting enabled for process: gpu-process
[0309/171505.198243:ERROR:gpu_memory_buffer_support_x11.cc(49)] dri3 extension not supported.
[0309/171508.645553:INFO:crash_reporting.cc(262)] Crash reporting enabled for process: utility
[0309/171511.298074:INFO:crash_reporting.cc(262)] Crash reporting enabled for process: renderer
[0309/171512.092380:WARNING:crash_reporting.cc(278)] Failed to set crash key: UserID with value: 0
[0309/171512.092600:WARNING:crash_reporting.cc(278)] Failed to set crash key: BuildID with value: 1709846872
[0309/171512.092613:WARNING:crash_reporting.cc(278)] Failed to set crash key: SteamUniverse with value: Public
[0309/171512.092624:WARNING:crash_reporting.cc(278)] Failed to set crash key: Vendor with value: Valve
[0309/171512.092635:WARNING:crash_reporting.cc(278)] Failed to set crash key: Platform with value: Linux
[0309/171512.094147:INFO:crash_reporting.cc(239)] Crash reporting enabled for process: utility
Requested Force create but SharedObjectMutex already created
Invalid browser dimensions: 0 x 0
Ssmcv 2024-03-12 github

This looks potentially bad:

[0309/171505.198243:ERROR:gpu_memory_buffer_support_x11.cc(49)] dri3 extension not supported.

The rest of the quoted messages seem to be normal.

Ssmcv 2024-03-12 github

@Chaussettes99, are you confident that the attached logs are from a time when the steamwebhelper was not working?

If you can reproduce this bug easily (it sounds as though you can), it would be helpful for you to do that, and then collect logs while that window is showing, without letting the steamwebhelper be restarted. That would make sure that the logs we're seeing are the logs that are relevant to the crash.

GPU: Nvidia GeForce GT 635

With which driver? The 525.147.05-7 proprietary driver from stable-updates, or the open-source Mesa/Nouveau driver, or something different?

Ssmcv 2024-03-12 github

Also, if you run Steam from a terminal like Konsole, you might see it uploading crash reports (it will say something like CrashID=abcdef1234). Pasting some of those crash IDs here would let a Steam developer look up what crashed and how.

Ssmcv 2024-03-12 github

The GT 635 is pretty old (2013, Kepler 2.0 architecture) and the Nvidia proprietary drivers often don't go so well with older hardware, so if you're able to upgrade, you might find that it would give you both a performance upgrade and fewer driver-related headaches on Linux. It doesn't have to be the latest and greatest: a used AMD GPU from a few years ago should work well with the open-source Mesa drivers and would probably be an improvement.

Kkisak-valve maintainer 2024-03-12 github

The last proprietary NVIDIA driver series to support the Kepler generation is the 470 series. Trying to use an NVIDIA 5xx driver series with that hardware will give you a bad time.

Ssmcv 2024-03-12 github

The last proprietary NVIDIA driver series to support the Kepler generation is the 470 series. Trying to use an NVIDIA 5xx driver series with that hardware will give you a bad time.

Ah, thanks for that reminder. If this is a GPU that needs the 470.x legacy driver branch, then it should probably already be considered to be "at risk".

CChaussettes99 2024-03-12 github

@Chaussettes99, are you confident that the attached logs are from a time when the steamwebhelper was not working?

If you can reproduce this bug easily (it sounds as though you can), it would be helpful for you to do that, and then collect logs while that window is showing, without letting the steamwebhelper be restarted. That would make sure that the logs we're seeing are the logs that are relevant to the crash.

GPU: Nvidia GeForce GT 635

With which driver? The 525.147.05-7 proprietary driver from stable-updates, or the open-source Mesa/Nouveau driver, or something different?

Here are some crash logs generated while the "steamwebhelper has stopped responding" window was open, the initial ones were from when I had already closed Steam.
steam-logs.tar.gz

There are 2 lines when running steam from konsole that contain crashID= strings:
assert_20240312141401_29.dmp[28176]: response: CrashID=bp-69a6adc5-f5f4-41fc-85e8-6bb382240312
assert_20240312141401_29.dmp[28176]: file ''/tmp/dumps/assert_20240312141401_29.dmp'', upload yes: ''CrashID=bp-69a6adc5-f5f4-41fc-85e8-6bb382240312''
Here is the full console output >
output.txt

And yes I do understand the GT 635 is quite old, but it's always worked with no issues for me up to this point and the 470 drivers are still supported by NVIDIA until later this year. This card is not able to use the 500+ series drivers unfortunately.

Thank you for getting back to me and trying to help.

Ssmcv 2024-03-12 github

Thanks for those logs. They still say dri3 extension not supported, and there's also this:

[0309/153637.712188:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglMakeCurrent: Failed to make the GLX context current
[0309/153637.713378:ERROR:gl_context_egl.cc(475)] eglMakeCurrent failed with error EGL_CONTEXT_LOST
[0309/153637.715572:ERROR:gpu_service_impl.cc(988)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.

and this:

[0309/154950.977034:ERROR:gl_surface_egl.cc(480)] eglCreateWindowSurface failed with error EGL_BAD_NATIVE_WINDOW

I think a steamwebhelper developer will need to take over investigating this; it doesn't look like obviously a SteamLinuxRuntime problem.

Ssmcv 2024-03-12 github

@kisak-valve, I think "... on Nvidia 470.x driver" might be a better thing to mention in the bug title than "... on Debian 12 Bookworm KDE"?

As a data point, the recent Steam betas have been running OK for me on a Debian 12 machine with GNOME, a newer GPU (a GTX 1070) and the newer 525.x driver series - so the fact that it's Debian 12 certainly isn't a problem, but 470.x vs. 525.x might be. (Or it could conceivably be KDE vs. GNOME compositor differences.)

Nothing extracted yet.