Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.6.0f3
Issue ID
898592
Regression
No
RAM usage remains high after instantiating lots of game objects and then exiting play mode
After instantiating many game objects, RAM usage rises as expected, but it doesn't drop to the previous level after exiting play mode.
Reproduction steps:
1. Open the attached project
2. Open task manager
3. Look at RAM consumed by Unity
4. Press play in Unity
5. Wait until game objects are loaded
6. Exit play mode
7. Look at RAM consumed by Unity in Task manager
Expected: RAM consumed before and after entering play mode is similar
Actual: RAM consumed after exiting play mode is far more than before entering play mode
Not reproduced on:
Reproduced on: 5.4.4f1, 5.5.3f1, 5.6.0f3, 2017.1.0a6
Results are much worse on Unity 2017. On 5.6 it at least somewhat drops after exiting play mode, but on 2017 RAM usage doesn't drop much after exiting play mode.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor and Android Player hangs/freezes when repeatedly Loading/Unloading AssetBundle in Vulkan
- Selecting a Material for HDRP Decal Projector in the Inspector window spams errors in the Console
- Expanded Asset Preview Box moves/hides when creating new Asset in Project window
- Player crashes on Meta Quest with "/apex/com.android/runtime/lib64/bionic/libc.so" when using OpenXR Plugin in a specific project
- The Editor's Help menu still lists an old/retired website - "Unity Forum"
Add comment