Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.3.2p3
Issue ID
776595
Regression
No
Profiler shows unnecessary entries when deep profiling
Profiler shows irrelevant data when profiling a method from a script with Deep Profile enabled.
Steps to reproduce:
1) Open the attached project 'Profiler.zip'.
2) Open scene '1.unity'.
3) Open the Profiler.
4) Enable 'Deep Profile'.
5) Play the scene for a brief moment and stop.
6) Select the very beginning of the profiler plot.
7) In the Overview of the Profiler, expand an entry named 'TestScript.Start().
8) Expand Profiler.BeginSample().
- The Start() function of the script 'TestScript.cs' is being profiled.
- Notice how the Profiler shows calls to BeginSample() and EndSample(), and the label given to the profiler entry in the script is only displayed after expanding several other entries. This makes deep profiling scripts difficult.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPropertiesChanged event fires before Player Properties are applied
- Opening Media Pop-out in “Before You Start” Tutorial throws “Styles” and “Styles_Dark” messages in the Console window
- Play Mode Scenario selection/highlight is too long and out of its bounds when the Play Mode Scenario window is opened after maximizing
- Asset name is not shown in the Undo History window when a sprite is modified
- Moving a Tab to a floating window fails when floating windows are docked next to each other
Add comment