Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2022.2.0a16
Issue ID
UUM-499
Regression
Yes
Duplicate Package Manager package description String Objects take up memory in the Editor
How to reproduce:
1. Create a new project
2. Open the Package Manager
3. Add the Memory Profiler package using the following package name (on older Editors that do not have the option to add a package by name, you need to use "Install package from git URL"): com.unity.memoryprofiler
4. Open the Memory Profiler, take a snapshot and select it
5. Select the "Objects and Allocations" tab
6. Right-click the "Data Type" column and press "Match..."
7. In the filter that appears above the table select "Is" in the dropdown and enter "Managed Object" in the input field
8. Right-click the "Type" column and press "Match..."
9. In the filter that appears above the table enter "System.String" in the input field
10. Right-click the "Size" column and press "Sort Descending"
11. Observe the table's entries in the "Name" column
Expected result: There are little to no duplicate entries with the same size and name values
Actual result: There are many duplicate entries of the same size and name related to the Package Manager
Reproducible with: 2020.3.23f1, 2020.3.35f1
Not reproducible with: 2019.4.39f1, 2020.3.22f1, 2021.3.3f1, 2022.1.2f1, 2022.2.0a14
Note: upgrading or downgrading an existing project to reproduce the issue sometimes causes the issue to no longer reproduce
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
- Shader warning in 'Hidden/Core/DebugOccluder' thrown after building High Definition 3D Sample Template
- Audio Mixer “+” buttons overlap with UI when the Audio Mixer window layout is set to Horizontal
- "Clear" button in the "Set project display name" closes all the pop-up instead of clearing just a name from the field
- Video Player renders no video on specific devices when using Vulkan
- The Editor slows itself down by showing tons of warnings when the majority of TransformAccessArrays content are NullRefs
Resolution Note:
It was already addressed and fixed in an internal ticket.
Resolution Note (2022.2.X):
It was already addressed and fixed in an internal ticket.