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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Add comment