Having entities view set to Runtime crashes the editor

Hello,

Having the entities view set to Runtime at first stops rendering the details panel after the first editor play. Just says there isn’t an entity representing the selected object, until the view is set to any other and back to Runtime. Running the editor when this happens crashes it.

Version: Unity 2022.2.8f1.
ECS: 1.0 pre.44

Regards,
A.

1 Like

You should file this as a bug report, and maybe share the stack trace here, too, so people can compare notes.

2 Likes
Obtained 32 stack frames
0x00007ff668bb8ed9 (Unity) ActiveEditorTracker_CUSTOM_Internal_GetActiveEditors
0x00000239a01151aa (Mono JIT Code) (wrapper managed-to-native) UnityEditor.ActiveEditorTracker:Internal_GetActiveEditors (UnityEditor.ActiveEditorTracker)
0x00000239a0115053 (Mono JIT Code) UnityEditor.ActiveEditorTracker:get_activeEditors ()
0x0000023aad63096b (Mono JIT Code) UnityEditor.InspectorWindow:GetInspectedObject ()
0x0000023b53088417 (Mono JIT Code) UnityEditor.PropertyEditor:OnDisable ()
0x0000023b53087feb (Mono JIT Code) UnityEditor.InspectorWindow:OnDisable ()
0x00000239a2d7cfc8 (Mono JIT Code) (wrapper runtime-invoke) object:runtime_invoke_void__this__ (object,intptr,intptr,intptr)
0x00007ffc5a930394 (mono-2.0-bdwgc) mono_jit_runtime_invoke (at C:/build/output/Unity-Technologies/mono/mono/mini/mini-runtime.c:3445)
0x00007ffc5a86eb44 (mono-2.0-bdwgc) do_runtime_invoke (at C:/build/output/Unity-Technologies/mono/mono/metadata/object.c:3066)
0x00007ffc5a86ecdc (mono-2.0-bdwgc) mono_runtime_invoke (at C:/build/output/Unity-Technologies/mono/mono/metadata/object.c:3113)
0x00007ff66953abe4 (Unity) scripting_method_invoke
0x00007ff66951b554 (Unity) ScriptingInvocation::Invoke
0x00007ff66951b63e (Unity) ScriptingInvocation::InvokeChecked
0x00007ff6695ab746 (Unity) SerializableManagedRef::CallMethod
0x00007ff669515ab0 (Unity) MonoBehaviour::WillUnloadScriptableObject
0x00007ff66950d524 (Unity) MonoManager::RemoveBehavioursFromManager
0x00007ff6695023ea (Unity) MonoManager::BeginReloadAssembly
0x00007ff66950d2f8 (Unity) MonoManager::ReloadAssembly
0x00007ff66a489abd (Unity) Internal_ADB_Only_ReloadAllUsedAssemblies
0x00007ff66a93d2ca (Unity) DomainReloadIfAllowed
0x00007ff66a93b43b (Unity) CompileAndDomainReload
0x00007ff66a959e32 (Unity) RefreshInternalV2
0x00007ff66a9624ff (Unity) StopAssetImportingV2Internal
0x00007ff66a4624f1 (Unity) EditorSceneManager::RestoreSceneBackups
0x00007ff66a148206 (Unity) PlayerLoopController::EnterPlayMode
0x00007ff66a158556 (Unity) PlayerLoopController::SetIsPlaying
0x00007ff66a15ada9 (Unity) Application::TickTimer
0x00007ff66a5e6eca (Unity) MainMessageLoop
0x00007ff66a5ebc70 (Unity) WinMain
0x00007ff66b9b89be (Unity) __scrt_common_main_seh
0x00007ffd017e26bd (KERNEL32) BaseThreadInitThunk
0x00007ffd0200a9f8 (ntdll) RtlUserThreadStart

Bug Report: CASE IN-35397

More info → Entity systems window is open during this operation.

If I manage to replicate it, I shall update this post.

1 Like

Hello! I just wanted to let you know that there is a fix for that crash that just barely missed the 2022.2.8f1 release. I went ahead and confirmed that it is indeed included in versions 2022.2.9f1 and onward. Sorry for the inconvenience, I know it’s a super annoying one!

1 Like

Thank you for a very quick reply. It’s appreciated. Just updated the Unity editor to the newest minor version. Hopefully that solves quite a few issues.