ValveSoftware / ValveSoftware/Fossilize

fosselize_replay eats all RAM when background processing shaders

Open
#210 21 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
780
Forks
78
PR merge metrics
No merged PRs in 30d

Description

This seems to happen in multiple games. Latest issue occurs with "Red Dead Redemption 2" as well as "The Elder Scrolls V: Skyrim Special Edition".

Both games, cannot complete shader processing with out eating all system memory.

System Details:

  • Memory: 64GB
  • CPU: i7-13700k
  • GPU: RX 6700 XT.
  • OS : Fedora 37
  • Kernel Version: 6.0.16-300.fc37.x86_64
  • Steam API: V020
  • Steam package version: 1671236931
  • Mesa: 22.3.2

Steam was installed from the rpmfusion.org repo.

The issue looks very similar to #194 , #198 or #84.

Something seems to cause it to not limit memory use. If I watch the memory use and enable/disable processing, you can aid it through this process as it is making progress. It just doesn't complete before it uses all memory.

Happy to help troubleshoot with direction. Haven't found anything particularly helpful in ~/.local/share/Steam/logs/shader_log.txt. Not sure how the manually run fosselize_replay to troubleshoot further.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing shader processing with Red Dead Redemption 2 or The Elder Scrolls V: Skyrim Special Edition while monitoring memory use. Review ~/.local/share/Steam/logs/shader_log.txt and investigate the manually run fosselize_replay path; done means processing completes without exhausting system memory.

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
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.