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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (fix version 0.7.0-preview.1):
Default sort order, thread sorting and 'state' sorting in change set