Error: Assertion failed on expression: ShouldRunBehaviour()

Hi! So suddenly I started to see this error in the editor, it doesnt seems to affect gameplay but it appeared out of nowhere.

This is the StackTrace that appears in the log:

7FF677767721 (Unity) StackWalker::ShowCallstack
0x00007FF6789DDBC5 (Unity) GetStacktrace
0x00007FF67988628E (Unity) DebugStringToFile
0x00007FF679885FA2 (Unity) AssertImplementation
0x00007FF6775CC5A2 (Unity) MonoBehaviour::InvokeMethodOrCoroutineChecked
0x00007FF6775C7BD9 (Unity) MonoBehaviour::smile:elayedStartCall
0x00007FF676B67601 (Unity) DelayedCallManager::Update
0x00007FF676F8157F (Unity) `InitPlayerLoopCallbacks'::`2'::PostLateUpdateScriptRunDelayedDynamicFrameRateRegistrator::Forward
0x00007FF676F69FA9 (Unity) ExecutePlayerLoop
0x00007FF676F6A080 (Unity) ExecutePlayerLoop
0x00007FF676F6F53C (Unity) PlayerLoop
0x00007FF67820325E (Unity) PlayerLoopController::UpdateScene
0x00007FF678202450 (Unity) Application::TickTimer
0x00007FF678A04B34 (Unity) MainMessageLoop
0x00007FF678A0DECE (Unity) WinMain
0x00007FF67A6D98F6 (Unity) __scrt_common_main_seh
0x00007FFF08897034 (KERNEL32) BaseThreadInitThunk
0x00007FFF0A342651 (ntdll) RtlUserThreadStart

However I cant figure what is happening, I think it might be that PlayerLoop is executing twice somehow? If anyone knows anything please let me know, thanks!

UPDATE: It seems to be coming from a Gameobject called “DelayedActionManager”, appearing in DontDestroyOnLoad scene, it didnt use to appear before. It seems to be related to the use of Addressables :open_mouth:
Anyone?

1 Like

I’m getting the same failing assertion and the editor logs tell this:
Assertion failed on expression: ‘ShouldRunBehaviour()’
(Filename: ./Runtime/Mono/MonoBehaviour.cpp Line: 856)

And yes, it came out of nowhere, and i think is highly related to addressables cause im struggling these days to make them working correctly.

I just had this same issue immediately after upgrading the Addressables package from 1.16.16 to 1.18.4. I had hundreds of the same Assertion failed error. I was able to fix it in my case by downgrading to 1.17.17.

I haven’t debugged it further or reported a bug because i have a deadline i’m working towards and 1.17.17 includes the synchronous API i needed. I might be able to come back to it and report it next week or later, but if someone else gets to it first that’d be great.