Search Issue Tracker
Fixed
Votes
0
Found in [Package]
1.0.0-preview.17
Issue ID
1362559
Regression
No
PackageManager memory leak when continuously opening the window
How to reproduce:
1. Open the attached project from "Compilation_PackageManager_Leak.zip".
2. Select the Memory Profile window.
3. Press the capture button a couple times: with Package Manger open, without and with again...
4. Compare the results and see if the third time Unity is using the same amount of memory.
Reproducible with: 1.0.0-preview.3-1.0.0-preview.17 (2019.4.30f1, 2020.3.18f1, 2021.1.20f1, 2021.2.0b11, 2022.1.0a8)
Expected result: Memory should not increase as all allocations should be cleared when the window is closed, or held to be reused when the window is re-opened.
Actual result: Memory increases every time the Package Manager window is opened.
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Issue fully fixed in 2022.1.0a15
Resolution Note:
Fixed in 2020.3.26f1
Resolution Note:
Fixed in: 2021.2.4f1