B4 and B5 become progressively slower entering play over time and editor crash on quit.

[hippocoder]

Is this a known thing? I ask since it happens on any project.

[LeonhardP]

Hey @hippocoder ,

Are these new issues or have you encountered any of them in previous 21.2 releases before? What version were you using before upgrading to 21.2 and encountering these problems? We’ll need more info to look into this so bug reports would be much appreciated.

Regarding progressively worsening enter playmode times:

@LeonhardP

Degradation of domain reload times during the lifespan of a specific editor session might also happen. Those can be caused by the creation of ScriptableObjects in the static constructor of a class with the [InitializeOnLoad] attribute or a method with [InitializeOnLoadMethod] attribute. What is happening in this case is that on domain reload ScriptableObject instances get restored and [InitializeOnLoad] gets called again causing an extra instance to be created and initialized.

In 2020.1 and up, one way to address this is to make the ScriptableObject a ScriptableSingleton. If you do not need this object to be a ScriptableObject, another alternative is to use a plain old C# object.

As mentioned before be mindful of the initialization of those objects created on load as it will impact your domain reload times.

For more information please have a look at our blog post about Tips for working more effectively with the Asset Database

[hippocoder]

I get it. This is probably actually a bug because while I am not actually using InitializeOnLoad at all, and I am not actually creating scriptable objects, [ExecuteInEditMode] is probably doing the same thing! pass this on to your engineers:

    [ExecuteInEditMode]
    public class Game : MonoBehaviour
    {
        public GameResources resources;

GameResources is a simple scriptableobject that gets domain reloaded constantly due to ExecuteInEditMode! But it is Unity’s bug in this case, or oversight that’s related.

I just don’t have time for a bug report today, too old and tired Thank you for the tip, pointed me to the only place I have scriptable objects.

I do not think [ExecuteInEditMode] was considered.

[hippocoder]

Actually disregard that. It is still happening. Longer and longer times to enter playmode with this pop up is the usual sign:

This does not occur in 2021.1 versions.

[LeonhardP]

This might be helpful if you want to investigate where the regression occurs:

@simon-ferquel-unity

Domain reload detailed timings can now be enabled in 2021.2.0a20 an 2021.1.11f1 (and we are busy backporting this to 2019.4 and 2020.3).

• In 2021.2.x it can be enabled using the diagnostics switches in Editor Preferences

• In 2021.1 (which does not have the diagnostic switches UI), you can enable it with the environment variable UNITY_DIAG_ENABLE_DOMAIN_RELOAD_TIMINGS.
  (e.g. in a Powershell console, you can run $env:UNITY_DIAG_ENABLE_DOMAIN_RELOAD_TIMINGS="1"; & 'C:\Program Files\Unity\Hub\Editor\2021.1.11f1\Editor\Unity.exe').

After that, in your editor logs (%LOCALAPPDATA%\Unity\Editor\Editor.log), you’ll see detailed timings on domain reload.