Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0b4
Issue ID
1004117
Regression
No
Undoing AddCompopnent for a behaviour with ExecuteInEditMode, doesn't call OnDestroy()
To reproduce:
1. Open the project, attached by the tester (OnDestroyEditMode.zip)
2. Add "NewBehaviourScript" script via Add Component in the Inspector to any object
3. Observe the console (Awake is called)
4. Ctrl + Z to undo the Add Component
5. Observe the console (OnDestroy isn't called)
Expected: OnDestroy gets called even when Monobehaviour has ExecuteInEditMode attribute
Reproduced in 5.6.5p2, 2017.1.3p1, 2017.2.2f1, 2017.3.1p2, 2018.1.0b4, 2018.1.0b9, 2018.2.0a1
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] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.