Search Issue Tracker
Fixed in 1.0.4
Votes
0
Found in [Package]
1.0.2
Issue ID
1286133
Regression
Yes
[Profile Analyzer]Timing Data mismatch is being reported when using frame links after loading matching data and pdata files
How to reproduce:
1. Open the attached '1286133.zip' project
2. Open Window > Analysis > Profiler
3. Load the 'Profiler.data' file into the Profiler (Assets > TestData > Profiler.data)
4. Open Window > Analysis > Profile Analyzer
5. Load the 'ProfileAnalyzer.data.pdata' file into the Profile Analyzer (Assets > TestData > ProfileAnalyzer.data.pdata)
6. Click on a frame link in the Frame Summary (located on the right of the Profile Analyzer window)
7. Observe the Console
Expected result: There are no messages in the Console
Actual result: The message indicating that the Timing data doesn't match appears in the Console
Reproducible with: Profile Analyzer 1.0.2, 1.0.3 (2020.1.0a11, 2020.1.12f1, 2020.2.0b9, 2021.1.0a2)
Not reproducible with: Profile Analyzer 0.5.0-preview.1, 1.0.1 (2018.4.28f1, 2019.4.13f1, 2020.1.11f1, 2020.2.0b9, 2021.1.0a2), 1.0.2, 1.0.3 (2018.4.28f1, 2019.4.13f1)
Cannot test with: Profile Analyzer 1.0.2, 1.0.3 (2020.1.0a1, 2020.1.0a9) (due to errors)
Notes:
- The issue does not reproduce if you pull the data from the Profiler into the Profile Analyzer
- The issue does not reproduce with files generated from the same version
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Animator Controller throws MissingReferenceException after undoing Layer Creation
- Full stack trace is always printed when an exception occurs in an IL2CPP build
- Licensing Client fails to launch when opening Unity Hub (licensing client path is not found)
- Licensing Client fails to launch when opening Unity Hub
- Different custom Shader behavior when GPU Resident Drawer is enabled
Add comment