Search Issue Tracker
Fixed in 0.6.1
Votes
0
Found in [Package]
0.5.1-preview.1
Issue ID
1401545
Regression
No
Colors of the Memory Usage Overview Memory Bars get mismatched after changing the sorting order
How to reproduce
1. Open the attached "PROF-1954" project
2. Open the "Window -> Analysis -> Memory Profiler" window from the menu
3. Select the "Test" Snapshot
4. Click on the Up/Down buttons under each Memory Usage category in the "Memory Usage Overview" section
Expected result: Memory Bars representing the Memory group are sorted in Ascending/Descending when the Up/Down button is selected, respectively
Actual result: Memory Bars colors are represented in an unknown order. For instance, one of the out-of-order Memory Bars are "Empty Fragmented Heap Space" and "Empty Active Heap Space" groups. The first size is more than the other one, but Memory Bars visualize the opposite
Reproducible with: 0.4.3-preview.1, 0.5.1-preview.1 (2019.4.36f1, 2020.3.30f1, 2021.2.13f1, 2022.1.0b9, 2022.2.0a5)
Couldn't test with: 0.4.2-preview.1 (2019.4.36f1, 2020.3.30f1, 2021.2.13f1, 2022.1.0b9, 2022.2.0a5) (selecting Up/Down doesn't change the color order)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 0.6.1):
Fixed in 0.6.1 (sorting is disabled)