Search Issue Tracker
Fixed
Votes
2
Found in
2020.3.41f1
2021.3.12f1
2022.1.21f1
2022.2.0b13
2023.1.0a16
Issue ID
UUM-17633
Regression
No
Crash on GameObject::ActivateAwakeRecursivelyInternal when opening project
Reproduction steps:
1. Open the user’s attached project
Expected result: The project opens
Actual result: Editor crashes
Reproducible with: 2020.3.41f1, 2021.3.12f1, 2022.1.21f1, 2022.2.0b13, 2023.1.0a10
Not reproducible with: 2023.1.0a11, 2023.1.0a16
Reproducible on: macOS Monterey 12.6 (M1 Max), Windows 10
Note: The user wrote that this started happening after adding a [SerializeField] Slider progressBar
First lines of the stack trace:
0x00007ff7a06caa75 (Unity) GameObject::ActivateAwakeRecursivelyInternal
0x00007ff7a06ca7f9 (Unity) GameObject::ActivateAwakeRecursively
0x00007ff7a06ca776 (Unity) GameObject::Activate
0x00007ff7a1c9a64c (Unity) DanglingComponentManager::ResolveDanglingComponents
0x00007ff7a0df2696 (Unity) AwakeFromLoadQueue::PersistentManagerAwakeFromLoad
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
- [Android][Vulcan] "UNITY_DISPLAY_ORIENTATION_PRETRANSFORM" is always 0 when the render pipeline is URP
- Editor loads for a long time when doing an Undo action in a large Shader Graph
- Memory leak when building AssetBundles
- [Asset Bundle] AudioSource output field not staying connected correctly when loaded from Asset Bundle
- [Android] Duolashock4 controller is not detected after disconnecting and reconnecting controller while the Player is running in the background
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-1291