Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a1
2019.3.0a3
Issue ID
1156118
Regression
Yes
OnDestroy() get's called twice for custom Editor Windows
OnDestroy() get's called twice for custom Editor Windows
To reproduce:
1. Open Unity
2. Open OnDestroyRepro project
3. OnDestroy/Open Me menu item
4. Close the newly opened editor window
Expected result: Console prints "OnDestroy() was called" only once
Actual result: it's printed twice
Reproduced on: 2019.3.0a1, 2019.3.0a3
Does not reproduce on: 2017.4.20f2, 2018.4.1f1, 2019.2.0b3
Comments (1)
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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Jon_Olive
Jan 29, 2020 19:11
This appears to still be happening in 2019.3.0f6