Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2018.4
2019.2
2019.3
2019.3.0f1
2020.1
Issue ID
1215235
Regression
No
Unmaximizing Editor Window results in a new window being created and deleted
How to reproduce:
1. Open attached project "Maximising EditorWindow Loses Static Instance.zip"
2. In Editor, click Test -> My Window
3. Observe newly-created window -> "Instance" field (the field is set)
4. Dock the window next to the Scene and Game windows
5. Right-click and Maximise it
6. Right-click and Un-Maximise it
7. Observe the Console window
7. It apparently creates a new window because "Set Instance = 1 (NewBehaviourScript)" gets logged.
7. But then it logs "OnDestroy 1" meaning the new window was immediately destroyed (not the old one).
8. And since step 6 set that new window as the static instance, it is now null so it stops working as a singleton.
Expected result: "Set Instance = 1" and "OnDestroy 0" are printed
Actual result: "Set Instance = 1" and "OnDestroy 1" are printed
Reproducible with: 2017.4.36f1, 2018.4.16f1, 2019.2.20f1, 2019.3.0f6, 2020.1.0a21
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
- [Linux] Player window unexpectedly resizes to monitor dimensions when calling "Screen.SetResolution" function with hardcoded resolution matching current display's width or height
- Color picker does not show the correct color when selecting color on the moving object
- “Asset X has no meta file, but it's in an immutable folder. The asset will be ignored.” errors are thrown when importing package with files not listed in package.json's "files" property
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
Resolution Note (2020.1.X):
Low priority defect and unlikely to be fixed for the near future.