Search Issue Tracker
Fixed in 1.0.3
Votes
0
Found in [Package]
0.6.0
Issue ID
1232208
Regression
No
[PA] Frame values go past their maximums when making a Selection bigger than the other graph with 'Pair Graph Selection' enabled
How to reproduce:
1. Create a new project
2. Import the Profile Analyzer package from the Package Manager
3. Open the Profile Analyzer window (Window -> Analysis -> Profile Analyzer)
4. In the Profile Analyzer window click the Compare tab and load the attached data (1.pdata and 2.pdata)
5. By clicking and dragging make a Frame Selection that has more frames than the other graph in total
Expected result: frame values should not exceed past their maximum values
Actual result: frame count and end frame values keep increasing past their maximum
Reproducible with: 0.4.0 - preview.5 (2018.4.20f1), 0.4.0 - preview.6 (2019.3.6f1), 0.5.0 - preview.1 (2020.1.0b2), 0.6.0 - preview.1 (2020.2.0a5)
Could not test with package versions: 0.4.0 - preview.3 (unable to load data)
Notes:
1. This issue does not occur when using keyboard commands (+, -, <, >) instead of dragging the selection
2. The frame count and end frame values are reverted to their correct values when the dragging is finished
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Add comment