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
- The "UnityWebRequest.result" of the "UnityWebRequestTexture.GetTexture" method changes when accessing "UnityWebRequest.downloadHandler" texture
- Slider rounding does not allow setting certain valid numbers as Values when Low and High Values not set to default
- UI Builder Canvas has too big resizing zone on the outside of the canvas
- GetCurrentAnimatorClipInfoCount() and GetNextAnimatorClipInfoCount() return 0 when animator is in transition
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
Resolution Note:
Issue fully fixed in 2022.1.0a15
Resolution Note:
Fixed in 2020.3.26f1
Resolution Note:
Fixed in: 2021.2.4f1