+2
Escalated

Getting weird delaying Plugin container init because database is not yet initialised

Andrew Scott 1 week ago updated 11 minutes ago 4

So right through the Beta 2019.3.0 versions I never saw this message and am now seeing it, it doesn't appear all the time, but when it does Unity hangs for about 5 mins give or take.

It usually appears when I double click any area that loads up Visual Studio 2019, you can not click on anything in the Editor while it is in this tight loop. Eventually the IDE will load up and then the following warning appears in the console.

This seems to only be happening since 2019.3.0f1 was released, never saw it on previous beta versions or other versions of Unity. And unlike what the message says, this is not a new project, even thought it was created in Unity 2019.3.0, I have been working on it for a few days now.

I am not sure if this helps or not, but I have had this Editor open for the last 2 days, but I doubt that has anything to do with it. But just in case it was one of those things that happens for longer periods of use.

Delaying plugin container initialization because asset database is not yet initialized.
This can happen after a project reimport or Unity upgrade.

UnityEngine.Debug:Log(Object)
Ludiq.PeekCore.PluginContainer:.cctor() (at Assets/Ludiq/Ludiq.PeekCore/Editor/Plugins/PluginContainer.cs:25)
UnityEditor.EditorAssemblies:ProcessInitializeOnLoadAttributes(Type[])

Unity Version:
2019.3.0f1
Peek Version:
1.1.5

I'm having the same thing, same version of Unity.

Same error here. same versions.

Delaying plugin container initialization because asset database is not yet initialized.
This can happen after a project reimport or Unity upgrade.

Escalated

Hi everyone,

This is actually a measure I put in place to prevent the plugin container from trying to load if the asset database from Unity isn't available yet. It happens usually on reimports, first imports or Unity version updates. It was a problem because it caused the setup wizard to fail to run.

The warning itself should not cause a hang or loop. I'm guessing it might be related to some other cause in your project, especially if the same editor instance was left open for two days. (Side personal note: I occasionally get the hang between Unity and Visual Studio myself in unrelated projects, usually when VS notices that the project has been modified by Unity and pops a dialog asking you whether you want to reload it. Answering that dialog usually fixes the hang).

Because the warning is harmless and everything should theoretically go fine afterwards, I'll just make it silent in the next version to avoid alarming users uselessly.

Which I can understand it happening if it did this as described, but how do you explain it showing up when you have been using Unity for about 2 hours and there was no update/imports?

And I have only started seeing this on the final release of Unity 2019.3.0 and never saw it on the beta versions. So I am guessing Unity has done something between the final beta version and the release version, that is causing this.