protonscr

Steam client won't quit for 2-10 minutes after playing doaxvv

steamclosed
ValveSoftware/steam-for-linux#11864 · opened 2025-04-01 by axis6404 · updated 2025-04-01 · 4 comments · github
Aaxis6404 2025-04-01 github

Your system information

  • Steam client version (build number or date): 1741737356
  • Distribution (e.g. Ubuntu): Debian bookworm-backports
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • GPU: Nvidia
  • Proton: 8.0-5

Please describe your issue in as much detail as possible:

Steam client won't quit for 2-10 minutes after playing doaxvv.
When I tell the Steam client to quit, access to the SSD goes to a busy state of nearly 100%.
The following errors are continuously logged in the system log:
steam[41760]: Thread "CJobMgr::m_WorkThreadPool:2" (ID 42157) failed to shut down

I checked using atop and fatrace and found 99% read access and 1% write access to the following file.
~/.steam/debian-installation/steamapps/shadercache/1361350/fozmediav1/video.foz (8.9GB)
This looks like a bug to me because of the abnormal read accesses. Please check if it is a bug or not.
This is an issue that's been around for over a year.
If I launch the Steam client and then exit the Steam client immediately without starting doaxvv, it takes 2 seconds to exit.

Steps for reproducing this issue:

(Proton 8.0-5)

  1. Launch "DEAD OR ALIVE Xtreme Venus Vacation"(doaxvv https://store.steampowered.com/app/1361350/DEAD_OR_ALIVE_Xtreme_Venus_Vacation/)
  2. Play beach volleyball once.
  3. Exit doaxvv.
  4. Exit the Steam client.
Kkisak-valve maintainer 2025-04-01 github

Hello @axis6404, this issue is already being tracked at #8113. Steam does close when the background task completes.

Closing as a duplicate.

Aaxis6404 2025-04-01 github

Please read carefully.
This is a bug report for a background task.

Aaxis6404 2025-04-01 github

I would add that the CPU usage of background tasks is low. (not video encoding).
Read access to the video cache forever before exiting.
Background tasks have completely meaningless accesses.
Probably a bug in the background task.

Aaxis6404 2025-04-01 github

@kisak-valve
I seem to have a different problem (shaders vs. video).
If I write to #8113 can you investigate this bug?

Proton versions