Search Issue Tracker
Fixed in 1.1.1
Votes
0
Found in [Package]
1.1.0-pre.2
Issue ID
1359686
Regression
Yes
Profile Analyzer doesn't ignore the last frame of the sequence
Reproduction steps:
1. Open the attached "1359686.zip" project
2. In the Profiler window click on the "Load from File" button
3. Load the attached .data file into the Profiler
4. In the Profile Analyzer window click on "Pull Data" button
5. In the Profile Analyzer window check the Frame Summary for "Min" amount
Expected result: Min is equal to around 12.7
Actual result: Min is equal to 0
Reproducible with: 1.1.0-pre.2, 1.1.0 (2019.4.29f1 ,2020.3.17f1, 18f1, 2021.2.0b8, 2022.1.0a5)
Not reproducible with: 1.0.3 (2019.4.29f1 ,2020.3.17f1, 18f1, 2021.2.0b8, 2022.1.0a5)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 1.1.1):
Pulling frame data from the Profiler to Profile Analyzer now excludes first and last frames if their main thread profiler data is incomplete, so that they don't skewer the analysis results