Search Issue Tracker
Fixed in 0.7.0-preview.1
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1244096
Regression
No
[Profile Analyzer] Incorrect details in Thread window are shown when loading data on top of existing data
How to reproduce:
1. Open attached "ProfilerAnalyzer" project
2. Open Profile Analyzer (Window->Analysis->Profile Analyzer)
3. In Profile Analyzer window select Compare tab
4. In the first slot load in user's attached "Profile Analyzer - Capture (2019.3.6f1).data.pdata" data
5. In the second slot load in user's attached "Profile Analyzer - Capture (2020.1.0b2).data.pdata" data
6. Open Threads window by pressing Select next to the Thread under Filters section
7. Observe Job.Worker thread
8. In the second slot load in user's attached "Profile Analyzer - 38 seconds (2019.3.10f1).data.pdata" data
9. Repeat steps 6 and 7
10. In the second slot load in user's attached "Profile Analyzer - Capture (2020.1.0b2).data.pdata" data
11. Repeat steps 6 and 7
Expected result: Job.Worker has 15 children
Actual result: Job.Worker has 31 children
Reproducible with: 0.4.0-preview.3, 0.6.0-preview.1 (2017.4.40f1, 2018.4.22f1, 2019.3.13f1, 2020.1.0b8, 2020.2.0a10)
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
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Resolution Note (fix version 0.7.0-preview.1):
Fixed thread count bug when using comparison mode and loading data on top of existing data.