Search Issue Tracker
Won't Fix
Votes
1
Found in
2018.4
2019.2
2019.3
2019.3.0b12
2020.1
Issue ID
1200372
Regression
No
Editor uses around 4.5 GB of memory and increases to 12 GB after the project is reloaded or tested with Memory Profiler package
Steps to reproduce:
1. Open user's attached project "Holes2.0.zip"
2. Open Profiler window
3. Select the Memory section
4. Notice the Memory usage from ManagedHeap.UsedSize, System.ExecutableAndDlls and ManagedHeap.ReservedUnusedSize
Expected results: ManagedHeap.UsedSize, System.ExecutableAndDlls and ManagedHeap.ReservedUnusedSize are not in Unity profiler Memory section
Actual results: ManagedHeap.UsedSize, System.ExecutableAndDlls and ManagedHeap.ReservedUnusedSize uses around 2 GB of memory
Reproducible with: 2019.3.0f1, 2020.1.0a15
Notes: Testing with Memory profiler package makes this project Run at around 12 GB of memory. 2018.2 and lower Unity does not load due to Memory issues and projet braking. Sometimes the Profiler window becomes black when selecting the Memory section.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Add comment