Search Issue Tracker
Fixed
Fixed in 2020.3.41f1, 2021.3.12f1, 2022.2.0b10, 2023.1.0a14
Votes
0
Found in
2020.3.39f1
2021.3.8f1
2022.1.14f1
2022.2.0b6
2023.1.0a8
Issue ID
UUM-12670
Regression
No
Memory usage increases when entering Play Mode with the Package Manager window open
Steps to reproduce:
1. Open the attached project “ScopedRegistryTest.zip“
2. Enter Play Mode
3. Open Window > Analysis > Memory Profiler
4. In the Memory Profiler window click “Capture New Snapshot“
5. Open Window > Package Manager
6. Enter Play Mode
7. In the Memory Profiler window click “Capture New Snapshot“
8. Select the snapshot that was made before opening the Package Manager
9. Click “Compare Snapshots“ and then select the snapshot that was made after opening the Package Manager
10. Open the “Objects and Allocations“ tab
Expected result: No memory usage increase caused by an open Package Manager window
Actual result: A memory usage increase caused by new “System.String“ types related to packages in the registry and the associated versions
Reproducible with: 2020.3.39f1, 2021.3.8f1, 2022.1.14f1, 2022.2.0b6, 2023.1.0a8
Reproducible on: Windows 10
Notes:
1. An open Package Manager window also has an impact on the time it takes to enter Play Mode
2. With a bigger registry of packages the memory usage and the time it takes to enter Play Mode increases
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Element UI disappears and NullReferenceException is thrown when dragging off the last or first element from the list in the Inspector
- [Silicon] Crash on ScriptableRenderLoopJob when machine is left idle while the Editor is in Play mode
- [Android] GraphicsBuffer.CopyCount does not work with Append Compute Buffer after Compute Shader Dispatch on some Android devices
- "DirectoryNotFoundException" error when building a project via script in one folder, then building via Editor in another, deleting the folder built via Editor and rebuilding via Script
- New items are created and old ones remain in memory when using 'treeView.SetRootItems(items)' and 'treeView.Rebuild()' which can cause a memory leak
Add comment