Crash with multiple stack traces when opening a Prefab Asset with missing scripts

Unity: Scene Management

This issue has been closed as a duplicate of:

Crash on PhysicsManager::SetBodyTransformChangeInterest when opening a scene

Open

2023.2.X

2022.3.X

Fixed

6.0.X

6000.0.0b15

Won't Fix

2023.3.X

2023.3.0b1 onwards

Reproduction steps:
1. Open the “users attached project”
2. Open the “Hotel1” Prefab Asset through the project window
3. Observe the crash

Reproducible with: 2022.3.14f1, 2023.3.0b1, 2023.3.0b3
Not reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.6f1, 2023.3.0a19
Fixed in: 2022.3.15f1

Reproducible on: macOS Sonoma 14.0 (Intel)
Not reproducible on: no other environment tested

First few lines of StackTrace:

#0  0x0000010d1f4be4 in GameObject::QueryComponentByType(Unity::Type const*) const
#1  0x0000010d3911cb in SetRenderNodeCullSceneMaskRecursively(Transform const&, unsigned long long)
#2  0x0000010d39122b in SetRenderNodeCullSceneMaskRecursively(Transform const&, unsigned long long)
#3  0x0000010d39122b in SetRenderNodeCullSceneMaskRecursively(Transform const&, unsigned long long)
#4  0x0000010d39122b in SetRenderNodeCullSceneMaskRecursively(Transform const&, unsigned long long)
#5  0x0000010d39122b in SetRenderNodeCullSceneMaskRecursively(Transform const&, unsigned long long)

at <unknown> <0xffffffff>
at UnityEditor.PrefabUtility:LoadPrefabContentsIntoPreviewScene_Injected <0x000eb>
at UnityEditor.PrefabUtility:LoadPrefabContentsIntoPreviewScene <0x0007a>
at UnityEditor.SceneManagement.PrefabStageUtility:LoadPrefabIntoPreviewScene <0x001fa>
at UnityEditor.SceneManagement.PrefabStage:LoadStage <0x00962>

Crash with multiple stack traces when opening a Prefab Asset with missing scripts

Unity: Scene Management

Open

Fixed

Won't Fix

Prioritise and Follow this issue

Have a workaround or additional info about this issue?

Crash with multiple stack traces when opening a Prefab Asset with missing scripts

Unity: Scene Management

Statuses

Open

Fixed

Won't Fix

Resolution Notes

Description

Prioritise and Follow this issue

Have a workaround or additional info about this issue?