Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.1.4f1
2020.2
Issue ID
1273031
Regression
No
Errors and inability to interact with window when docked and redocked
Reproduction steps:
1. Open attached project "Charts.zip"
2. In Menu, open Test/Test Window
3. Dock the Test Window above the Game View
4. Observe Console window
5. Dock the Test Window next to the Inspector window
6. Observe and try to close/interact with the previous and current positions of the Test Window
Expected results: No errors, ability to interact with and close the Test Window
Actual result: "ObjectDisposedException" console error, inability to interact, only closes after second "Close Tab" action
Reproducible with: 2019.4.10f1, 2020.1.6f1, 2020.2.0b3
Could not test with: 2018.4.27f1 (console errors break project)
Notes:
1. When relaunching Unity, the "ghost" window, docked above the Game View, loads without problem
2. Repositioned Test Window closes after the second "Close Tab" action
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note:
UI Elements are not persisted (nor their data or states) so it's up to the user to ensure the survival of associated data. UI Elements are always recreated so you cannot rely on them to survive a domain reload or a simple recreation.