Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4
2020.2
Issue ID
1244286
Regression
No
Profiler still collects samples and the Editor memory usage continuously increases when Play Mode is paused
How to reproduce:
1. Create a new project
2. Open the Profiler window (Window -> Analysis -> Profiler)
3. In the Profiler window enable 'Deep Profile' and 'Call Stacks' (issue reproduces without this step but it makes easier to reproduce)
4. Enter the Play Mode and then pause it
5. Open the Windows Task Manager
Expected result: according to the Windows Task Manager the amount of memory used by the Unity Editor does not change drastically
Actual result: the amount of memory used by the Unity Editor continuously increases
Reproducible with: 2018.4.23f1, 2019.3.15f1, 2020.1.0b10, 2020.2.0a12
Notes:
The Profiler displays no new data
-
DavoMyan
Jun 25, 2021 14:19
Still having this same issue in 2020.2.0f1 when exiting play mode,
https ://i.imgur . com /WMP0LMA .png
Task manager even shows memory usage of 18gb
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash when attempting to create a custom FMOD DSP unit
- [Linux] Floating windows do not keep their size after restarting the Editor
- .framework plugin is mistakenly treated as a directory when building for Universal Windows Platform
- Artifacts appear on GameObjects when using the WebGL Player on Silicon macOS
- Only the icon of the disabled child GameObject is faded when a parent GameObject is a Prefab
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a16
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b15
Resolution Note (fix version 2019.4):
Fixed in 2019.4.3f1