Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
1
Found in
2020.3.48f1
2021.3.25f1
2022.2.19f1
2023.1.0b16
2023.2.0a14
Issue ID
UUM-35196
Regression
No
“OnDisable” function is executed based on script order in the Inspector window but not Script Execution Order
How to reproduce:
1. Open the user’s attached “TestOrder.zip” project
2. Enter Play Mode and exit Play Mode
3. Observe the Console window
Expected result: “First OnDisable”, “Second OnDisable”, and “Third OnDisable” are logged
Actual result: “Third OnDisable”, “First OnDisable”, and “Second OnDisable” are logged
Reproducible with: 2020.3.48f1, 2021.3.25f1, 2022.2.19f1, 2023.1.0b16, 2023.2.0a14
Reproduced on: macOS 13.2.1 (Intel)
Note: Not reproducible with the “OnEnable” function
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
- Shader Compiler IPC Exception and Editor Crash on AMD 9000-X3D CPU series
- Editor crashes in TextLib::FindIntersectingLink when hovering UITK Labels with <link> tags rendered via ATG
- Crash on mono_log_write_logfile when more than one copy of bee_backend is running
- NativeList<T>.ParallelWriter.AddNoResize() causes memory corruption when used in a [BurstCompile] IJobParallelFor on Web builds
- Realtime reflection probe changes light strength when removing light sources using URP WebGL
Resolution Note:
Changing the execution order of OnDisable() to respect ScriptExecutionOrder would be a breaking change.
Resolution Note (2023.2.X):
Changing the execution order of OnDisable() to respect ScriptExecutionOrder would be a breaking change.