Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2018.4.0f1
2018.4.3f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1172305
Regression
Yes
Crash on CanDestroyObject when opening a project for the first time
How to reproduce:
1. Extract and open the "case_1172790repro.zip" Unity project in version 2018.4.3f1
2. Observe the crash
Reproducible with: 2018.4.6f1, 2019.1.14f1, 2019.2.2f1, 2019.3.0a12
Not reproducible with: 2017.4.32f1
Notes:
1. Stack traces of the crash may vary from version to version - in version 2018.4.3f1 it crashes on "CanDestroyObject", on 2018.4.6f1 - "ImmediatePtr<Unity::Component>::operator*", on 2019.1.14f1 - "Unity::Component::GetGameObject", on 2019.2.2f1 - "GameObject::ActivateAwakeRecursivelyInternal", on 2019.3.0a12 - "GetPrefabDynamicDependencies". All stack traces seem to have the line "DestroyObjectHighLevel" in common (apart from 2019.3.0a12).
2. Only reproducible when launching the project for the first time on the device.
3. On version 2017.4.32f1, the issue cannot be reproduced - launching project for the first time does not result in a crash. The Console tab indicates a YAML syntax error in a Prefab Asset.
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a15.
Resolution Note (fix version 2019.3):
Fixed in 2019.3.5f1