Search Issue Tracker
Fixed in 2019.4.X
Votes
38
Found in
2019.4.12f1
2019.4.13f1
Issue ID
1287233
Regression
Yes
An error is thrown when maximizing the Scene/Game view after changing the Layout of windows and re-opening the project
How to reproduce:
1. Create a new project
2. Change the Layout in the Editor by moving and docking windows to different places
3. Close and re-open the project
4. Maximize the Game view by pressing on the vertical ellipsis in the top right of the Game view and then pressing Maximize
Expected results: No errors are thrown
Actual results: The "Invalid editor window UnityEditor.FallbackEditorWindow" error is thrown in the Console
Reproducible with: 2019.4.12f1, 2019.4.14f1
Not reproducible with: 2018.4.28f1, 2019.4.11f1, 2020.1.0a1, 2020.1.11f1, 2020.2.0b9, 2021.1.0a3
Notes:
- Entering the Play Mode while Maximize On Play is enabled will throw the error as well
- Resetting the Layout (by choosing any of the Layouts from the drop-down Layout list) will throw the "Failed to destroy editor windows: #1" error in the Console and will stop the other error from appearing when maximizing the Game view
-
wlwl2
Oct 30, 2020 19:44
Layout is causing a lot of warnings/errors with Unity 2019.4.x (I don't remember when it started) and only lasts for one session/is not persisting/you have to manually select a saved layout every time you open Unity. I am using 2019.4.13f right now.
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
- [URP][Lighting] The skybox doesn't render after changing the settings of the Material when using the URP Render Pipeline
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
Resolution Note (fix version 2019.4):
Fixed in 2019.4.15f1