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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment