ValveSoftware / ValveSoftware/Fossilize
100 GB shadercache folder
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 780
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Hello, I hope this is the right place for this issue since I'm not 100% the problem is on your part.
So I'm running an Arch Linux system under Wayland. Installed wine/proton with Steam and activated the background shader processing.
I noticed that my ~/.local/share/Steam/steamapps/shadercache folder has grown over the last few weeks to ~100 GB.
The only game I'm running is Warframe, which is less than 50 GB.
Upon starting the game it does the usual "processing vulkan shaders" which I reckon takes a full hour with 100% usage of each of my CPUs, thus I activated the background shader processing feature which sometimes starts this software and uses 50% of my CPU.
Is this size expected behavior? It's seems quite unlikely to me that the game needs to cache (more than double its full size) of vulkan shaders.
Thank you for your time
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 reproducing the shadercache growth described for ~/.local/share/Steam/steamapps/shadercache with Warframe, Steam background shader processing, and Vulkan shaders on Arch Linux under Wayland. Determine whether the reported size is expected behavior or indicates a Fossilize issue; done means documenting the cause or a specific, reproducible defect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- arch-linux
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100