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
Comments (1)
-
ZerroCoolll
Dec 10, 2022 02:50
Running coupon Lennox crash 10 lines into code yg
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-1291