protonscr

Steam client it consumes more than 50% of my AMD 5950x CPU doing nothing

steamclosed
ValveSoftware/steam-for-linux#12265 · opened 2025-08-13 by Phil995511 · updated 2025-08-14 · 6 comments · github
PPhil995511 2025-08-13 github

Your system information

  • Steam client version (build number or date): 1754956157 and previous stable versions from +/- 2~3 months ago
  • Distribution (e.g. Ubuntu): Debian 13 (mother of Ubuntu)
  • Opted into Steam client beta?: [Yes/No] Yes, with out success the problem is still present
  • Have you checked for system updates?: [Yes/No] Yes
  • Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs] tar: Child returned status 2
    tar: Error is not recoverable: exiting now
  • GPU: Nvidia/Intel/AMD Nvidia RTX 5070 ti

Please describe your issue in as much detail as possible:

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

For the past 2~3 months when I launch my Steam client it consumes more than 50% of my AMD 5950x CPU doing nothing.

Sometimes the bug appears as soon as Steam starts, and sometimes it occurs after a game update. It's very annoying in terms of noise because my CPU fans start spinning loudly. It costs a lot of electricity, slows down other tasks on my system, and wastes resources.

It almost feels like I'm running a cryptocurrency miner...

Please find a solution to this, especially since it's the middle of summer and my CPU is running at 92°C when it's under such stress in game...

Best regards.

PS

If you could improve the support for MSF2020 on Linux, I would be very grateful. Windows keeps crashing on my PC and I can only use Linux until I find a solution to my problem...

Steps for reproducing this issue:

  1. Start Steam client
  2. If all is ok (without bug), run a game update, normally after this the bug coming
  3. If after this procedure the bug still not present, restart Steam client and restart the procedure
PPhil995511 2025-08-13 github
Image
Kkisak-valve maintainer 2025-08-13 github

Hello @Phil995511, without information on what threads are using resources, this looks like you're showing fossilize using 25% of the CPU for background shader pre-caching. This is the normal intended amount and should be interrupted when you start a game.

You can control if Steam does background shader pre-caching at Steam -> Settings -> Downloads -> toggle Allow background processing of Vulkan shaders on or off. Also, you can monitor the activity of that subcomponent in its log at ~/.steam/steam/logs/shader_log.txt.

PPhil995511 2025-08-14 github

I've never encountered such a problem before, and I've been a customer of yours for a very long time. In fact, I read that you tried to mitigate it in an article or a log, but the problem persists...

This problem occurs without launching any game, it also manifests itself after exiting a game. It does not stop unless you kill the Steam client.

Does it speak more to you in this form ?

Regards

Image
Kkisak-valve maintainer 2025-08-14 github

Eight fossilize_replay threads on a 32 core system is confirmation that this is indeed the shader pre-cache subsystem warming your video driver's on-disk shader cache. Steam using this amount of resources is within expectations and as previously noted, you can turn off background processing of Vulkan shaders if you don't want it to do that. You also have the option to turn of that subsystem entirely beside the toggle for background processing.

PPhil995511 2025-08-14 github
Image
PPhil995511 2025-08-14 github

Ok thanks I found I disabled the preloading of shaders in the "Download" section. It should be disabled by default... if every time I launch steam you recalculate the shaders of all my installed games it quickly becomes a bit complicated for us... or we have to use our machines much less when doing it. Greetings.

Nothing extracted yet.