[FIXED] Big spikes in Editor making the game untestable

Unity Engine
, ,
1

Unity version used : 2020.3.22f1

Every time an object instance (using a pooling system) in our gameplay screen spawn, the editor drops to 10 -15 fps making it untestable.

In the screenshot attached below, V sync has been disabled and target frame fps too.

When v sync was enabled and the target frame rate was set to 60, the spikes did come from WaitForTargetFps but now apparently, the pike comes from EditorLoop, I have no idea what to look for.

The spikes don’t seem to happen in build.

A bit of help would be welcoming as it is making our production workflow way slower.

Thanks!

-Jordi Roca

8304873--1089396--upload_2022-7-23_14-45-54.png
8304873--1089396--upload_2022-7-23_14-45-54.png1390×729 107 KB

2

The same is happening in the 2021.3.6f1 version.

8304957--1089405--upload_2022-7-23_15-44-38.png
8304957--1089405--upload_2022-7-23_15-44-38.png1357×714 107 KB

8304957--1089405--upload_2022-7-23_15-44-38.png
8304957--1089405--upload_2022-7-23_15-44-38.png1357×714 107 KB

3

Update:

Profiling the Editor instead of Playmode just gave me more info on what is inside Editor Loop.
As you can see the EditorApllication.Internal_CallHierarchyHasChanged() is the origin of those Spikes.

8306631--1089624--upload_2022-7-24_11-14-41.png
8306631--1089624--upload_2022-7-24_11-14-41.png1366×768 136 KB

8306631--1089621--upload_2022-7-24_11-12-5.png
8306631--1089621--upload_2022-7-24_11-12-5.png1359×612 112 KB

4

More info with deep profiling:

8306634--1089627--upload_2022-7-24_11-23-24.png
8306634--1089627--upload_2022-7-24_11-23-24.png1378×748 125 KB

5

Update: Issue fixed
It was caused because of the Febucci Hierarchy plugin, disabling “Update In Play Mode” fixed it.

1 Like