Search Issue Tracker
By Design
Votes
0
Found in
2018.4.32f1
2019.4.21f1
2020.2.5f1
2021.1.0b7
2021.2.0a4
Issue ID
1315545
Regression
Yes
[Profiler] Raw Hierarchy PlayerLoop entries unfold automatically when folded during Play Mode profiling with Live option enabled
How to reproduce:
1) Create a new Unity project
2) Open the Profiler window
3) Select CPU Module, Raw Hierarchy
4) Enter Play Mode and enable Live profiling
5) Sort the detail panel entries by name
6) Unfold 'PlayerLoop' entry
7) Attempt to fold it
Expected result: PlayerLoop is folded and stays folded
Actual result: PlayerLoop is folded, then unfolds itself
Reproducible with: 2018.4.32f1, 2019.4.21f1, 2020.2.5f1, 2021.1.0b7, 2021.2.0a4
Not reproducible with: 2018.4.31f1, 2019.4.0f1, 2019.4.20f1, 2020.2.0a1, 2020.2.4f1, 2021.1.0a1, 2021.1.0b6, 2021.2.0a1, 2021.2.0a3
Could not test with:
Notes:
Hierarchy does not seem to be affected, only Raw Hierarchy
Before this regression, when folding the details panel during live profiling the entries could still rarely unfold, but after this regression, it happens consistently
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (2021.2.X):
To be able to carry the expansion states between Hierarchy and Raw Hierarchy views, as well as from frame to frame within either of these views, the only consistent points of reference are the Profiler Marker IDs of the Profiler Samples shown as Items in the hierarchical TreeView.
With this bug fix:
https://issuetracker.unity3d.com/issues/profiler-playerloop-call-is-automatically-expanded-in-raw-hierarchy-when-profiler-dot-collecteditorstats-is-expanded-in-hierarchy
The process of carrying the expansion state across the views and frames became consistent and reliable, based on that Marker ID. It always tried to do that but mostly failed, thus this behavior turned from a random blip to something that can be consistently reproduced.
There is no other data point we could use to counteract this slightly and seemingly unexpected behavior in Raw Hierarchy in any consistent form, so this is pretty much By Design.
Workaround: switch to Hierarchy view, collapse the tree item you want to collapse and then switch back to Raw Hierarchy.