Search Issue Tracker
Feature Request
Feature Request in 2020.2.X
Votes
0
Found in
2020.2.6f1
Issue ID
UUM-7387
Regression
No
Scripting Code not Auto-Instrumented when run in a custom PlayerLoop delegate and using Deep Profiling
No description entered in Cloud incident.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
We've considered the issue and concluded that this is behaving as it should at this moment, but we have filed it as a feature request to insert instrumentation for custom PlayerLoop delegates.
The current workaround is to manually place ProfilerMarkers in custom PlayerLoop delegates to get them to show up in the profiler, or to turn on Deep Profiling.
Resolution Note (2020.2.X):
We've considered the issue and concluded that this is behaving as it should at this moment, but we have filed it as a feature request to insert instrumentation for custom PlayerLoop delegates.
The current workaround is to manually place ProfilerMarkers in custom PlayerLoop delegates to get them to show up in the profiler, or to turn on Deep Profiling.