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
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
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.