You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I managed to get a very nasty error by accidentally putting a MonoInstaller in the list of PrefabInstallers (attached to SceneContext).
This is a user error, in that I just wasn't paying enough attention when I added the installer, but it did result in Unity freezing for quite a while and then printing Zenject Exception: Assert hit! 999+ times to the console.
Aside from locking Unity up for a minute or two the error message is less than obvious (especially for a beginner).
Steps to reproduce:
Add SceneContext
Create MonoInstaller
Add MonoInstaller as component of SceneContext gameobject
Add MonoInstaller to PrefabInstaller list
Run project
Without ever having touched the prefab installer before, I'm guessing this causes it to instatiate itself in an infinite loop.
I'm running Unity 2019.1.14f1 (though I doubt that matters).
The text was updated successfully, but these errors were encountered:
vertis
changed the title
UserError -> StackOverflow AssertHit! (999+ times)
User Error -> StackOverflow AssertHit! (999+ times)
Oct 17, 2019
It is maintained by the original Zenject author and unlike ModestTree who only know how to sue, but not provide support for "their" software, he actually still maintains Zenject. Just post your question there and you will most likely get an answer.
I managed to get a very nasty error by accidentally putting a MonoInstaller in the list of PrefabInstallers (attached to SceneContext).
This is a user error, in that I just wasn't paying enough attention when I added the installer, but it did result in Unity freezing for quite a while and then printing
Zenject Exception: Assert hit!
999+ times to the console.Aside from locking Unity up for a minute or two the error message is less than obvious (especially for a beginner).
Steps to reproduce:
Without ever having touched the prefab installer before, I'm guessing this causes it to instatiate itself in an infinite loop.
I'm running Unity 2019.1.14f1 (though I doubt that matters).
The text was updated successfully, but these errors were encountered: