Search Issue Tracker

Fixed in 2019.4

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

-

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

  1. Response avatar

    Resolution Note (fix version 2019.4):

    Fixed in 2019.4.15f1

Comments (16)

  1. 02ed8bed96490b00f8cf8aadec35b8e0?d=mm

    wlwlz

    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.

  2. F2de6bfca843df622c553b03292a36aa?d=mm

    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

  3. 94de33cfb138b8d1052092839e4ddc24?d=mm

    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.

  4. 27c43f5e718723bfd694f06d36745744?d=mm

    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.

  5. 5b87e4a9ca6544a31cf6b8e7bca68fb9?d=mm

    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...)

  6. 5b87e4a9ca6544a31cf6b8e7bca68fb9?d=mm

    Vicious_Cat069

    Nov 19, 2020 10:18

    Same here, 2019.4.12f1
    Just reinstalled - if I'd have come here first it would've saved me an hour!

  7. 543ad2e1415537d5afd2c91ccc042c51?d=mm

    djpippin35

    Nov 19, 2020 06:43

    I'm running dual monitors Win10, on unity 2019.4.13f1 and getting the same issue. The problem I'm having now is not just the can't destroy editor, but it seems to have broke my project as well. Neither the factory reset or changing layouts is helping at all.

  8. 02ed8bed96490b00f8cf8aadec35b8e0?d=mm

    wlwlz

    Nov 18, 2020 07:28

    Whilst you are fixing this, please do a check with dual monitors and Windows 10 if you can.

  9. 175d765e2063baadacecb3ee1a1ab172?d=mm

    caveDweller

    Nov 13, 2020 20:52

    I am getting this error on version 2020.1.12f1. Please advise the fix for this.

  10. 76115af98d11a568278e9e476bda1bce?d=mm

    DSam

    Nov 13, 2020 16:48

    This bug exactly as described is happing in the 4.14f as well. All the best.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.