Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
0
Found in
2019.3
2019.3.13f1
2020.2
Issue ID
1246653
Regression
No
Selecting a scripting sample in the CPU Profiler Timeline doesn't highlight it in the chart when the name is simplified
How to reproduce:
1. Create a new project
2. Open the Profiler window (Window -> Analysis -> Profiler)
3. Load the attached Profiler data (timeline-selection-highlight-bug.data)
4. In the Profiler Modules drop-down select only 'CPU' Module to be displayed
5. In the chart select the last frame (300)
6. Make sure the Profiler display is set to 'Timeline' (use the top-left dropdown in the details panel)
7. Make sure the 'Show Full Scripting Method Names' option is disabled (there's an 'additional options' drop-down list in the far right of the details panel)
8. In the Timeline panel select GUIUtility.ProcessEvent() sample
Expected result: the chart highlights frames 283, 300
Actual result: the chart does not highlight any frames
Reproducible with: 2019.3.14f1, 2020.1.0b9, 2020.2.0a11
Could not test with: 2018.4.23f1 ('Show Full Scripting Method Names' option not introduced)
Workaround:
Enable 'Show Full Scripting Method Names', then deselect and select GUIUtility.ProcessEvent() sample again
Notes:
The issue occurs only with scripting methods (blue samples)
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
- "Unknown managed type referenced" error is thrown on Play Mode enter with Profiler recording
- CapsuleCast from certain positions fails to detect a hit
- ShaderUtil.GetShaderData(shader).SubshaderCount does not count unsupported subshader
- GameObject.GetComponents returns the wrong number of components
- GUI button looks different from Editor in a Build
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a12
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b10
Resolution Note (fix version 2019.3):
Fixed in 2019.3.15f1