Search Issue Tracker
By Design
Votes
0
Found in [Package]
0.7.1-preview.1
1.1.0
Issue ID
PROFB-194
Regression
No
Memory Profiler memory usage is not freed when it's window is closed
How to reproduce:
1. Open the “MemoryCaptureMemoryIssue” project
2. Open the Task Manager and take note of the memory used by the Editor
3. Open the Memory Profiler (Window > Analysis > Memory Profiler)
4. In the Memory Profiler window open the “SOTFSNP” snapshot
5. Repeat step 2
6. Close the snapshot and the Memory Profiler window
7. Repeat step 2
Expected result: The memory usage by the Editor should return to the level noted in step 2
Actual result: The memory usage by the Editor remains elevated, similar to the level noted in step 5
Reproduced with: 0.7.1-preview.1 (2021.3.33f1), 1.1.0 (2022.3.15f1, 2023.2.4f1, 2023.3.0a19)
Reproduced on: Windows 11, macOS 12.6.1 (M1)
Not reproduced on: No other environment tested
Notes:
1. On macOS the Activity Monitor can be used to monitor the memory usage
2. Reproducible in a new project
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 and a window with "GetManagerFromContext: pointer to object of manager 'MonoManager' is NULL (table index 5)" error is shown when launching a freshly created project
- Editor Windows dragging behavior is erratic/glitchy when a specific multi-display setup is used and the Editor window is not on the main display
- Meta Quest missing an icon in Build Profiles window in U6.0
- Foldout arrow indent is misaligned in the Inspector when used for Arrays or Lists
- Material import pipeline strips properties when it is added with a script
Resolution Note:
We will not be aiming to fix this issue. Once we have loaded a snapshot in the memory profiler, we allocate memory to process it. Much of this memory will be cleared and re-used by the Editor process, but releasing it all back to the system would be a complicated and time consuming job and we feel our time is better spent working on other issues and features.
Depending on exactly what you're trying to achieve, you may be able to work around this issue by opening a second instance of the Unity Editor to view snapshot data.