Unity Issue Tracker - An error is thrown when maximizing the Scene/Game view after changing the Layout of windows and re-opening the project

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

Scene/Game View

Oct 23, 2020

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

Resolution Note (fix version 2019.4):

Fixed in 2019.4.15f1

Comments (21)

levidavidmurray

Mar 10, 2022 22:25

I'm seeing this constantly in 2021.2.11f1
drcfrx

Nov 27, 2021 18:54

This is NOT fixed in 2019.4.32f1
Gaspedal

Sep 29, 2021 17:54

Same here with 2021.1.16f1

When I open my project and play it (maximize on play enabled) then it works.
When I click on my Terrain in the Hierarchy then it dont start and I get this Error.
When I reset my Layout then it works again, even when I click on my Terrain GameObject.
When I close my project and reopen itm, then I can start it. When I click on my Terrain then same Error. After Layout reset it works again until next reload of the project.

Without "maximize on play" it works always.
AlanMattano

Aug 05, 2021 20:50

is this related?
https://forum.unity.com/threads/how-to-debug-invalid-editor-window-unityeditor-fallbackeditorwindow-unityeditor-editorapplication.395044/#post-7391894
Seith

Dec 05, 2020 13:09

Just to be clear: The bug is still there in 2019.4.16f1 and happens any time you maximize a window.

The only way to get rid of it is to nuke ALL of your existing layouts (Revert Factory Settings) and painstakingly recreate them all by hand.

Then you can maximize again a window without getting the error.
wlwl2

Nov 23, 2020 18:56

I did get the

`GUI Error: You are pushing more GUIClips than you are popping. Make sure they are balanced.
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)`

error a few times, but I don't remember why and when, and I'm not sure how to reproduce that. It clears nicely and doesn't cause any problems though.
Sui42

Nov 23, 2020 15:26

Most of these errors have indeed been fixed in .15f1

However, I sometimes get this error when I create a script, which might be related:

GUI Error: You are pushing more GUIClips than you are popping. Make sure they are balanced.
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

I saw a similar issue tracker here:

https://issuetracker.unity3d.com/issues/creating-a-new-c-number-script-throws-an-error-when-project-window-is-set-to-one-column-layout-and-vs-solution-is-generated
Nothke

Nov 20, 2020 13:44

Can confirm it has been fixed in .15f1. Once you reset the layout to factory settings, the error no longer comes back, even after restarting the editor.

Btw, this error was invoked prior to .15f1 every time ANY window was maximized, not just Scene or Game view and not just when Playing.
Liderangel

Nov 19, 2020 19:52

A layout fix was deployed in .15 (references another Issue Tracker). Can anyone confirm if that fixes this? Maybe they are related.
Vicious_Cat069

Nov 19, 2020 11:12

No way of editing a comment?
I've just installed 2019.4.15f1 and the problem seems to have vanished (it happened once when I started for the first time, but I've just rebooted twice and no bug...)