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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Add comment