Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.2.X, 2021.1.X
Votes
0
Found in
2018.4
2020.1.0a12
2020.2
2020.2.0a8
Issue ID
1242253
Regression
Yes
[Profiler] playerLoop call is automatically expanded in Raw Hierarchy when Profiler.CollectEditorStats is expanded in Hierarchy
How to reproduce:
1. Create and open a new project
2. Open the Profiler window with CPU module active
3. Enter Play mode for a few seconds
4. Exit Play mode
5. Select the "Raw Hierarchy" view mode in the CPU module of Profiler and make sure that all of the "playerLoop" calls are collapsed
6. Select the "Hierarchy" view mode and expand the "Profiler.CollectEditorStats" Call
7. Select the "Raw Hierarchy" view mode
Expected result: the "playerLoop" call is still collapsed
Actual result: the "playerLoop" call is expanded
Reproducible with: 2018.4.22f1, 2019.3.0a5, 2020.1.0a12, 2020.1.0b8, 2020.2.0a9
Not reproducible with: 2019.3.0a6, 2019.3.12f1, 2020.1.0a11
Could not test with: 2017.4.40f1 and earlier (no "playerLoop" call in the Profiler)
Notes:
-This reproduces in other ways, for example:
a) Expanding "playerLoop" call in "Raw Hierarchy" view mode expands "Profiler.CollectEditorStats" call in "Hierarchy" view
b) Collapsing calls instead of expanding
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
- Profiler - Taking you to the wrong section when using 'show'
- Draw Renderers custom pass doesn't work with SSGI
- WebCamTexture does not set the requested resolution when used in WebGL
- Editor default Stylesheet/Matching Selector buttons in Debugger don't do anything
- Graphics.DrawMeshNow stops rendering Render Texture after a few frames when viewed in the Player
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a4
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b6
Resolution Note (fix version 2020.2):
Fixed in 2020.2.5f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.21f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.32f1