Search Issue Tracker
Fixed in 1.1.0-pre.2
Votes
0
Found in [Package]
0.6.0-preview.1
Issue ID
1230558
Regression
No
[Profile Analyzer] Console warning when using Compare and clicking the First Frame link of data with a high frame number
Reproduction steps:
1. Open attached project "ProfileAnalyzer.zip"
2. Enter Play Mode
3. After the frames reach 4-digits, in Profiler window, stop the recording
4. Exit Play Mode
5. In Profile Analyzer window, go to Compare mode
6. For the first set of data, load "capture1.pdata"
7. For the second set of data, Pull Data
8. In Marker Summary window, click on the link for the second set of Data
9. Observe Console window
Expected result: No warning is logged
Actual result: "Timing data in profiler doesn't match" warning is logged
Reproducible with: 2018.4.20f1, 2019.3.7f1, 2020.1.0b3, 2020.2.0a5
Could not test with: 2017.4.38f1 (package version unavailable)
Reproducible with package versions: 0.4.0-preview.5, 0.6.0-preview.1
Could not test with package versions: 0.4.0-preview.3 (console errors)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment