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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
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