Quest: free memory drops with every save load

Open
  • Is something wrong?
#489 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
49/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
android, csharp, unity
Domain
game-dev, performance

Research direction

Reproduce on a Quest 3 release build by loading the same Khorinis save several times and watching Free= with adb logcat -s VrApi. The issue suggests using a development build with the Unity Memory Profiler to compare snapshots before and after a load. Done means confirming whether memory keeps dropping and identifying what remains retained; the issue does not name code files or tests.

Written by the indexing model from the issue text.

Description

bug
Description

On the Quest 3, free system memory drops with every save load and doesn't come back. Possibly the previous world's objects or textures aren't released.

Expected Behavior

Free memory after a save load is about the same as after the first load.

Actual Behavior

G2 at 120 Hz, Khorinis: free memory (Free= in adb logcat -s VrApi) fell from about 1.4 GB to 0.9 GB over two save loads (6.8 s and 7.1 s loads, two minutes apart) and stayed there. A few more loads could get the app killed.

Reproduction Steps
  1. Quest build, G2, load a save in Khorinis.
  2. Load the same save 3-4 times in a row.
  3. Watch Free= in adb logcat -s VrApi after each load.

Environment Information

  • Reproducibility: Seen once (two loads); needs a check
  • Platform: Quest 3 (release build, IL2CPP)
  • Game Version: main 83a1aebd2 + local integration branch
Notes

To find what stays: a development build with the Unity Memory Profiler, comparing snapshots before and after a load.
Not checked against BoroBongo's work.

Dominant language
C#
Stars
33
Forks
1
Avg merge
1d 17h
Merged PRs (30d)
51

Getting set up

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 Gothic-Unity-Project/Gothic-Unity

All issues in Gothic-Unity-Project/Gothic-Unity

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.