Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.3.4f1
Issue ID
805169
Regression
No
CPU spikes from CanvasScaler.Update when using 'Constant Physics Size'
Reproduction steps:
1. Open the attached project
2. Open the available scene
3. Play scene
4. Open the profiler
5. Observe the CanvasScaler.Update() function in 'CPU Usage'
Result: When Canvas Scaler UI Scale Mode is set to 'Constant Physics Size', CanvasScaler.Update() call time is much larger than any other setting. Frequent CPU spikes also occur.
Note: User describes spikes reaching up to 10 ms (provided video)
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