[Shadow of the Tomb Raider] fossilize eats all RAM until it OOMs

Open
#194 11 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
tooling

Research direction

No source file, test, or entry point is named. Reproduce fossilize background processing with Shadow of the Tomb Raider while monitoring memory, and compare the behavior with the fix referenced in issue #84. Done means processing completes without exhausting system memory or requiring background processing to be toggled.

Written by the indexing model from the issue text.

Description

The symptoms here seem to be the same as #84 but that one was fixed and closed, so I was asked to file a new issue.

In the last month or two, I've noticed that fossilize seems happy to consume all system memory without bounds, and this is particularly evident with Shadow of the Tomb Raider (native Linux version), which consistently sees fossilize gobble up all the memory and then eventually get OOM killed and you have to kick it by turning background processing off and on again. It does eventually complete because it doesn't start from zero each time, but it makes the system unusable for anything else until it finally completes. I've been preemptively turning background processing off and on while watching the memory usage to get it to complete a bit faster, but that's no fun.

I suspect that the behaviour here is not unique to SotTW - it's just that this seems to have enough work to do that it can saturate my system.

System Details:

  • CPU: Core i9-12900K
  • Memory: 64GB (no swap)
  • GPU: Nvidia 515.48.07
  • OS: Ubuntu 22.04 with 5.18.4 mainline kernel
  • Steam Client: Beta 2022-06-18 00:17:34 1655513879

Thanks.

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

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.

More from ValveSoftware/Fossilize

All issues in ValveSoftware/Fossilize

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.