Search Issue Tracker
Fixed in 1.0.0
Votes
0
Found in [Package]
0.6.0-preview
Issue ID
1246860
Regression
No
Profile Analyzer 'total number of markers' value gets affected by filtering when switching to Compare tab
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 'capture.pdata' into both slots
5. In the Marker List right-click on PlayerLoop Marker and select 'Set as Parent Marker Filter'
6. Open the Single tab
Expected result: total unique markers in the data sets (the 2nd value next to the Analyze/ Compare button) are identical in Single and Compare tabs
Actual result: the Single tab value is constant while the Compare tab value gets affected by filtering
Reproducible with: 0.5.0 - preview.1 (2018.4.23f1, 2019.3.14f1), 0.6.0 - preview.1 (2020.1.0b9, 2020.2.0a11)
Could not test with package versions: 0.4.0 - preview.3, 0.4.0 - preview.5, 0.4.0 - preview.6 ('Set as Parent Marker Filter' command not introduced)
Notes:
Both values should either get affected by filtering or stay constant
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
- Skinned Mesh Renderer with multiple Animator Components does not render when "Optimize Game Objects" is enabled
- [iOS]Certain characters are not displayed when using iOS devices with 18 OS and newer
- Trees do not render in 'Unity Terrain - URP Demo Scene'
- Silent crash when clicking in Scene View in a specific project
- The Player renders black on a Quest headset when MSAA, Post Processing, and Spacewarm depth submission are enabled
Resolution Note (fix version 1.0.0):
Fixed to use the unfiltered count