Search Issue Tracker
Duplicate
Votes
0
Found in
5.3.0f4
Issue ID
753928
Regression
Yes
When editor is closed, EditorWindow.OnDestroy is called if window is not docked
To reproduce:
1. Open Window/MyEditorWindow
2. Close the Unity Editor
3. Assets/Test.txt is written by OnDestroy as expected
4. Open the Unity Editor again. OnEnable reports that the file exists and deletes it for further testing.
5. Dock the MyEditorWindow in with the project and console windows
6. Close the Unity Editor
7. This time, OnDestroy is not called and Assets/Test.txt does not get created.
Expected result: EditorWindow.OnDestroy is not called when editor is closed (seeing as that is the case in 5.2.3p2).
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
- Editor crash on "PPtr<Shader>::operator Shader*() const" when checking in changes with a very long comment in Unity Version Control window
- [Ubuntu] Toolbar and menu items for Version Control lack spaces in text on Linux
- Unity Version Control window Pending Changes tab’s Item checkbox is unresponsive when clicked and the item list is empty
- Audio stuttering occurs when heavy processing is performed while OnAudioFilterRead is in use
- Inconsistent Node search results in VFX Graph
This is a duplicate of issue #752684