Quest: free memory drops with every save load

未關閉
#489 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 2 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
49/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
android, csharp, unity

研究方向

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.

由索引模型根據 Issue 內容生成。

描述

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.

主要語言
C#
星號
33
分支
1
平均合併
1 天 21 小時
30 天內合併 PR
56

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

Gothic-Unity-Project/Gothic-Unity 的其他 Issue

查看 Gothic-Unity-Project/Gothic-Unity 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。