Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.2.0f3
Issue ID
967994
Regression
Yes
UI elements causes CPU usage spikes and makes Editor laggy
How to reproduce:
1. Open the attached project
2. Open the scene
3. Notice the Editor lag
4. Open the profiler
5. Notice the CPU usage spikes
Expected result: The Editor is not lagging.
Actual result: The Editor is lagging.
Note: The CPU usage spikes are caused by UI_Manager gameObject.
Reproducible with: 2017.2.0f3. 2017.2.0b7,
Regression introduced in: 2017.2.0b7.
Not reproducible with: 5.6.4p2, 2017.1.2p3, 2017.2.0b6, 2017.2.0p1, 2017.3.0b9, 2018.1.0a4.
---------------------------
Fixed in: 2017.2.0p1.
Comments (2)
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Rachan
Mar 26, 2018 18:54
from 2017.3.1 Still not fix!
duplexius
Jan 25, 2018 10:06
NOT FIXED