Search Issue Tracker
Won't Fix
Votes
3
Found in
2018.4
2019.2
2019.3
2019.3.0f4
2020.1
Issue ID
1206572
Regression
Yes
2017.4 - 2019.3 Editor UI redraw performance regression
Reproduce
1. Create a new project
2. Open layout "Window > Layouts > Default"
3. Open Profiler Window
4. Change Profiler from Playmode to Editor and start recording
5. Constantly resize the Inspector panel
6. Stop Profiler
7. Observe the CPU timings of the profiling session
Actual result: UI drawing is significantly slower in Unity 2019.3.0f4 than in 2017.4.34f1
Expected result: Faster or at least the same editor UI performance as earlier Unity releases
Notes:
The issue is hard to reproduce on a high-end computer.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2020.1.X):
The issue is because of the addition of a profiler marker for PlayerLoopController::UpdateScene() which is added in the later versions(2019.1 and above)