Search Issue Tracker
Fixed in 0.7.0-preview.1
Votes
0
Found in [Package]
0.5.0 - preview.1
Issue ID
1228078
Regression
Yes
Profile Analyzer - List of Threads is not strictly ordered
How to reproduce:
1. Create a new Unity project
2. Import the Profile Analyzer package
3. Using the Unity Profiler record some frames of the Editor
4. Pull the profiling data into the Profile Analyzer
5. Open the 'Threads' drop-down
Expected result: the threads are ordered alphabetically
Actual result: the threads are not strictly ordered
Reproducible with: 2018.4.19f1, 2019.3.6f1, 2020.1.0b2, 2020.2.0a3
Could not test with: 2017.4.38f1(package unavailable)
Reproducible with package versions: 0.5.0 - preview.1, 0.6.0 - preview.1
Not reproducible with package versions: 0.4.0 - preview.6
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 0.7.0-preview.1):
Default sort order, thread sorting and 'state' sorting in change set