ValveSoftware / ValveSoftware/Fossilize
104GB RAM Usage during "stuck" Processing Vulkan Shaders at 100%
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 780
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Your system information
-
Steam client version (build number or date): 1764106918
-
Distribution (e.g. Ubuntu): Arch
-
Opted into Steam client beta?: Yes
-
Have you checked for system updates?: Yes
-
Steam Logs: steam-logs.tar.gz
-
GPU: Nvidia
Please describe your issue in as much detail as possible:
Steam is spawning multiple processes leading to 104GB RAM usage during "Processing Vulkan Shaders" while being stuck at 100%. I observed this for about 10 minutes and watched it reach 123GB out of 124GB multiple times and froze the system. Processing Vulkan shaders never completed, just sat there at 100% with this insanely high RAM usage.
Steps for reproducing this issue:
- Launch Spider-Man 2
- Let Vulkan Shaders process
- Observe RAM usage and system freeze
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached Steam logs and reproducing the Vulkan shader-processing path described in the issue with Spider-Man 2 on Arch and an Nvidia GPU. Trace the processes created while processing is stuck at 100%; done means shader processing completes without runaway memory usage or freezing the system.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100