Search Issue Tracker
Active
Under Consideration for 1.2.X
Votes
0
Found in [Package]
1.2.3
Issue ID
PROFB-339
Regression
No
Profile Analyzer - Values not matching Hierarchy
Whilst testing highlights it looks like the Profile Analyzer might be listing some things incorrectly
The below is from: https://drive.google.com/file/d/1rsPi4d1E-EBE5aKqYqx4nOlLQbKuDxuF/view?usp=drive_link
Frame 559
Looking at Profiler.FlushCounters
Profile Analyzer says self time is 1.96
!image-2025-06-16-09-40-45-169.png|thumbnail!
Hierarchy says self time is 0
!image-2025-06-16-09-41-35-640.png|thumbnail!
Steps to reproduce:
- Load attached file into the Profiler
- Pull Data into the Profile Analyzer
- Go to Frame 559
- Compare Profile Analyzer vs Hierarchy
- Notice how Profiler.FlushCounters looks to be shown differently between the two
\\
Actual results: Values do not match
Expected results: Values should match
\\
Reproducible with versions:
Not reproducible with versions:
Can’t test with versions:
\\
Tested on (OS):
\\
Notes:
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- IndexOutOfRangeException occurs when entering "<a></a>" tags in a TextMeshPro UI field
- Numeric property drag cursor gets enabled in the Inspector Preview window when the window is above numeric properties
- UI elements become unusable due to Object and Text Fields being set to empty/"0" when clicking "Reset" on their Components
- Scene Asset is not attached to a Lighting Data Asset for a URP Package Sample Scene
- Gizmos are not rendered for the Base Camera when using Camera Stacking
Add comment