Search Issue Tracker
Fixed in 2022.1.X
Votes
2
Found in
2018.4
2019.4
2020.3
2020.3.0f1
2021.1
2021.2
2022.1
Issue ID
1347557
Regression
No
Editor crashes on GameObject::ActivateAwakeRecursivelyInternal when opening a specific scene
Reproduction steps:
1. Open the project from the attached google drive link
2. Go to Assets/Scenes and open "Level_1.unity" scene
Reproducible with: 2018.4.36f1, 2019.4.29f1, 2020.3.14f1, 2021.1.15f1, 2021.2.0b4, 2022.1.0a2
First lines of the stack trace:
0x00007ff72bfe6255 (Unity) GameObject::ActivateAwakeRecursivelyInternal
0x00007ff72bfe5fd9 (Unity) GameObject::ActivateAwakeRecursively
0x00007ff72bfe5f56 (Unity) GameObject::Activate
0x00007ff72e265f7b (Unity) DanglingComponentManager::ResolveDanglingComponents
0x00007ff72cf65484 (Unity) AwakeFromLoadQueue::InvokeCheckConsistency
Notes:
- Deleting the Library folder did not help
- The crash happens only when opening the "Level_1.unity" scene
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
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a14