Search Issue Tracker

Active

Planned for 2020.1, 2020.2

Votes

3

Found in

2018.4

2020.1

2020.2

Issue ID

1275751

Regression

No

Allocated memory is not cleared when loading and unloading scenes

Scene Management

-

How to reproduce:
1. Open the attached project ("case_1275751-Memory-Test.zip")
2. Open a profiler window
3. Make a Standalone Development build with Autoconnect Profiler and Script Debugging enabled
4. Launch the build
5. Check the initial memory footprint in the profiler
6. Click the "Cubes Scene" button to load the scene
7. Inspect memory footprint in the profiler after the scene is loaded
8. Click the "Clean Scene" button to load an empty scene
9. Compare current memory footprint with a freshly loaded project on step 5

Expected result: Memory footprint goes back to initial value or close to it
Actual result: Memory footprint significantly increases

Reproducible with: 2018.4.27f1, 2019.4.11f1, 2020.1.7f1, 2020.2.0b4

Notes:
1. The issue eventually causes out of memory crashes on Switch
2. Both UnloadUnusedAssets and GC.Collect are called after scene unload, and it can be called again by pressing the Spacebar key

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.