Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.2
Issue ID
1071836
Regression
Yes
[Profiler] Timeline UI Performance Regression
With the change to allow for scrolling and resizing the threads in the Timeline view of the profiler came a performance regression. Since there was a change in the logic of how this is displayed, this is somewhat expected but particularly the way in which the maximum thread depth is calculated is suboptimal and can be a bit costly.
How to Reproduce:
1. Deep Profile the editor while looking at the CPU timelineview of the profiler
2. continuously press the "Current" button
3. stop profiling and examine the result of the profiler
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment