Search Issue Tracker
Duplicate
Votes
0
Found in
2020.1
2020.1.0b12
Issue ID
1254400
Regression
Yes
<CallDelay> Call appears when entering in PlayMode and causes performance regressions for Editor Play Mode
When profiling the Editor in 2020.1, a <callDelay> section appears highlighted in editor play-mode that causes a laggy experience in editor.
Attached -photos and recording of side by side profiling of entering play mode for both 2019.4 and 2020.1
Repro steps:
- download this project
- turn on editor profiling
- enter play mode
- after that, pause and scrub the timeline and notice that <CallDelay> take up 89% of the CPU on enter play mode.
For more complicated projects, that delay is really really large, as these forum posts suggest
https://forum.unity.com/threads/editor-loop-high-thread-utilization-on-play-mode.899840/
https://forum.unity.com/threads/2020-1-0b11-unresponsive-and-extremely-choppy-in-play-mod.906608/
Not reproducible in 2019.4 or 2020.2.0a14
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ResizeScriptingList<ScriptingObjectPtr> when passing an undeclared variable to the results parameter for GameObject.FindGameObjectsWithTag
- [Android] "Screen.safeArea.y" always returns values outside of the Safe Area when the device is in Portrait orientation
- Frame spike due to many TreeRenderer.TreeUpdated calls when repositioning terrains in large Scenes
- Crash on GameObject::RemoveComponentFromGameObjectInternal when reparenting Text GameObjects
- [IL2CPP-GarbageCollector] Changing GCMode might permanently disable GC in a multithreaded context
Add comment