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
- [Discussions] "NativePassData.GraphPasses()" has GC Alloc of ~256 B when using Render Pass
- Setting Shader Graph to Surface Type "Transparency" and Render Face "Both" breaks the preview
- Warning "Unknown pseudo class "multiline"" is logged when the Animator is loaded or in use after picking Motion in a States Inspector
- Deleting the property in the Blackboard and then creating the different type property with the same name throws an error
- Selector gets stuck in UI if scroll is used while dragging
Resolution Note (fix version 0.6.1):
Fixed in 0.6.1 (sorting is disabled)