Search Issue Tracker
Fixed in 1.0.4
Votes
0
Found in [Package]
1.0.2
Issue ID
1268597
Regression
Yes
[Profile Analyzer] Threads are not loaded correctly in a pulled data when Profiler data was loaded
How to reproduce:
1. Open the attached "ProfileAnalyzer" project
2. Open the Profiler (Window->Analysis->Profiler)
3. Load the attached "A.data" file into the Profiler
4. Open the Profile Analyzer (Window->Analysis->Profile Analyzer)
5. In the Profile Analyzer press the "Pull Data" button
6. Open the Threads menu (In the Profile Analyzer under the Filters section next to the "Threads:" press the "Select" button)
Expected results: All Threads are loaded correctly
Actual results: Only the Main Thread is shown
Reproducible with: 2020.1.0a11, 2020.1.2f1, 2020.2.0a20 (1.0.2, 1.0.3)
Not reproducible with: 2018.4.26f1, 2019.4.8f1, 2020.1.0a9 (1.0.0, 1.0.3), 2020.1.0a11, 2020.1.2f1, 2020.2.0a20 (1.0.0, 1.0.1)
Notes:
- If the Profiler data was recorded (not loaded in) and then pulled in to the Profile Analyzer the Threads will be loaded correctly
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment