ValveSoftware / ValveSoftware/Fossilize
Why is fossilize always running?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 780
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
I have a 12 core Ryzen 5900x and only a few games on my computer, but it seems that steam is constantly running fossilize.
How on earth does it take my computer 28mins to compile a fully featured Linux kernel, but after rebooting, Steam spends hours processing who knows what?
I just cannot fathom this order of magnitude of required processing, Especially considering steam never even bothers to update my games, so I cannot fathom why It would need to spend so long processing shaders from World of Tanks and Apex Legends (and Noita/Factorio if that even counts as OpenGL titles).
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
The report names Steam, Fossilize, and the games World of Tanks, Apex Legends, Noita, and Factorio, but no source file, test, or entry point. Start by reproducing the prolonged processing and determine which Fossilize operation is involved. Done would require a clearly scoped, reproducible problem and an agreed expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, performance
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100