Quest: free memory drops with every save load

Aberta
#489 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
49/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
android, csharp, unity
Domínio
game-dev, performance

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
C#
Estrelas
33
Forks
1
Merge médio
1d 17h
PRs com merge (30d)
51

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de Gothic-Unity-Project/Gothic-Unity

Todas as issues de Gothic-Unity-Project/Gothic-Unity

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.