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