Search Issue Tracker
Won't Fix
Unknown (hidden) 2019.4.X, 2020.1.X
Votes
0
Found in
2019.4.39f1
2020.1.0a19
Issue ID
UUM-11862
Regression
No
GameObject not disbled when changing the sibling order inside OnDisable
1. What happened
If we change the sibiling order of an object inside OnDisable, it can cause that some objects aren't disabled during DestroyObject.
This leads to a lot of undefined behaviours.
This is due to how we iterate the objects in https://github.cds.internal.unity3d.com/unity/unity/blob/93a364f095f55c0e7616dc8d1638d6c6c37b5ad5/Runtime/BaseClasses/GameObject.cpp#L212
2. How we can reproduce it using the example you attached
- Open SampleScene
- Enter play mode
Expected behaviour:
- Both objects log from OnDisable
Actual Behaviour:
- Only Child1 logs from OnDisable
- The editor might crash due to trying to destroy an enabled GameObject
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
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
- Animator window Eye button on click visual does not cover the whole area of the button when clicked
Resolution Note:
The bug is not reproducible in Version: 2020.3.40f1 which is now the legacy LTS.