Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.3.X
Votes
0
Found in
2018.4
2019.3
2019.3.0f6
2019.4
2020.1
2020.2
Issue ID
1249893
Regression
No
Crash on UnpackPrefabInstanceRecursive when entering Play mode in a Scene with broken prefabs
Reproduction steps:
1. Open the project attached by the user
2. Open "SampleScene"
3. Enter Play mode
Reproducible with: 2018.4.23f1, 2019.3.16f1, 2019.4.0f1, 2020.1.0b11, 2020.2.0a13
First lines of the stacktrace:
0x00007FF6C4E218B1 (Unity) UnpackPrefabInstanceRecursive
0x00007FF6C4E2193F (Unity) UnpackPrefabInstanceRecursive
0x00007FF6C4E18770 (Unity) DestroyObjectHighLevel_Internal
0x00007FF6C4E1859E (Unity) DestroyObjectHighLevel
0x00007FF6C4E02209 (Unity) DestroyWorldObjects
Notes:
- The prefabs in the scene were likely broken by a github merge
- Before the crash multiple errors are shown:
Transform has 'SpriteRenderer' change interests present when destroying the hierarchy. Interests must be deregistered in Deactivate.
(Filename: C:\buildslave\unity\build\Runtime\Transform\Transform.cpp Line: 58)
Transform has 'Renderer::kSystemParentHierarchy' hierarchy interests present when destroying the hierarchy. Interests must be deregistered in Deactivate.
(Filename: C:\buildslave\unity\build\Runtime\Transform\Transform.cpp Line: 59)
Assertion failed on expression: '!gameObject.IsActive()'
(Filename: C:\buildslave\unity\build\Runtime/Misc/GameObjectUtility.cpp Line: 1561)
Transform has 'm_ColliderTransformChangeSystemHandle_TRS' change interests present when destroying the hierarchy. Interests must be deregistered in Deactivate.
(Filename: C:\buildslave\unity\build\Runtime\Transform\Transform.cpp Line: 58)
Transform has 'm_ColliderTransformChangeParentHierarchy' hierarchy interests present when destroying the hierarchy. Interests must be deregistered in Deactivate.
(Filename: C:\buildslave\unity\build\Runtime\Transform\Transform.cpp Line: 59)
- Might be similar to case 1204389
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some VFX Window Panels close on entering Play mode
- VFX Graph using Redo action for Move and Connect node results in an unknown input value
- VFX Parameters are missing the documentation links
- Node name gets cut off in the Visual Effect Graph when the name is long
- Custom Particle System names textboxes are not correctly wrapped in the VFX Control panel
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a2
Resolution Note (fix version 2020.3):
Fixed in 2020.3.8f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.28f1