Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
5
Found in
5.2.1p3
Issue ID
736075
Regression
Yes
5.2/5.3 CPU usage is doubled when instantiating UI prefabs compared to 5.1.X
Reproduction steps:
1. Open attached project
2. Open the profiler window
3. Open and play the "Untitled" scene
4. Click the button "Button" twice (it will instantiate 10 UI prefabs)
5. The CPU will spike to about 47 ms (which is twice as much than in 5.1.X, 20 ms)
Expected result: The spike should be only up to about 20 ms like in 5.1.X
Note: In 5.2.0f1 (89160207ce1a) the spike is up to 65 ms
Regression starts from: 5.2.0f1 (89160207ce1a)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment