Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.3.0f4
Issue ID
769265
Regression
No
Unresponsive profiler in a frame that has a lot of data
Steps to reproduce:
1) Open users attached project.
2) open profiling and enable deep profiling
3) After one second, a script will execute a very deep call and create a peak in the profiler.
4) Select the peak.
5) Now try to drag the profiler window or click items. It should be much slower than normal.
Actual: it takes around .5s for every click in the profiler regardless of whether you are expanding or just selecting
Expected: it shouldn't 'lag' navigating editor unless you are expanding or changing something in the editor
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