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
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
Add comment