Search Issue Tracker
Fixed
Fixed in 2022.3.22f1, 2023.2.15f1, 6000.0.0b11
Votes
0
Found in
2022.3.20f1
2023.2.8f1
2023.3.0b5
6000.0.0b11
Issue ID
UUM-62792
Regression
No
"MissingReferenceException: The object of type 'UnityEditor.DockArea' has been destroyed but you are still trying to access it." is thrown when maximizing the Game view window
How to reproduce:
1. Open the attached project "Ruined.zip"
2. Double-click on the Game view window tab
Expected results: No errors are thrown in the Console window
Actual results: "MissingReferenceException: The object of type 'UnityEditor.DockArea' has been destroyed but you are still trying to access it." is thrown
Reproducible with: 2023.2.8f1, 2023.3.0b5
Could not test with: 2021.3.35f1, 2022.3.19f1 (compilation errors in the Console window)
Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment