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
- “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