I keep getting Failed to destroy editor windows: #1 errors no matter what I do

Unity Engine
,
1

Error:
Failed to destroy editor windows: #1
FallbackEditorWindow
UnityEditor.<>c:b__28_0()

I keep getting this error. I restarted Windows & unity, reinstalled unity, reset factory settings, reset layout, nothing works.

Also when I start my game the something happens and the screen goes black or the PC completely dies. I think I ruled out the gpu because it works perfectly when running at maximum power with demanding games like the Witcher 3. (My scene that crashes it is just some simple cubes&capsules with a player controller)

2

Hi @erdostamasa ,

Is the same error happening if you create an empty project?

1 Like
3

I have created a new project, it doesn’t have the error. I went back to the project I was working on, apparently the error only happens there. When I open it, I get this warning:

The editor layout could not be fully loaded, this can happen when the layout contains EditorWindows not available in this project
UnityEditor.WindowLayout:LoadDefaultWindowPreferences()

And when I revert the layout to factory settings I get the mentioned

Failed to destroy editor windows: #1
FallbackEditorWindow
UnityEditor.<>c:b__28_0()

error

1 Like
4

Are you using any plugins?

This is maybe happening because a custom Editor window is not loading properly.

If that’s the case, my recommendation is to create a new project where you can copy all of your assets gradually.

You can do it in the next order:

  • Create a new project
  • Add all the Unity’s packages
  • Add all the Unity’s Asset Store assets
  • Add the rest of 3rd party assets from other sources
  • Add all your project assets, except the scripts
  • Add your Editor scripts
  • Finally, add the rest of your scripts

In each step, Unity will compile / import what you have on your project one step at a time, so you’ll be able to detect when the issue is happening.

Once you found the step in where you have the problem, you can try to refine your search by adding the assets of such a step gradually.

I hope this helps!

2 Likes
5

That project was a test project where I followed a tutorial so it’s not that important to keep it. If I encounter this error in any of my other projects, I will use these steps to solve it. Thanks for your answers, they were really helpful!

2 Likes
6

@DiegoDePalacio_1
Hi! I started a completely new project with a fresh install of Unity and I got the

Invalid editor window UnityEditor.FallbackEditorWindow
UnityEditor.EditorApplicationLayout:FinalizePlaymodeLayout()

error. I don’t have any extensions/plugins and I’m using the default layout.
If I revert to the factory settings the error stays and I again get the

Failed to destroy editor windows: #1
FallbackEditorWindow
UnityEditor.<>c:b__28_0()

error. This is a really fustrating problem because I can’t find the source of it no matter what I do. I use two monitors, Unity is maximized on the main monitor and I ususally got the documentation open on the second one. Could this have to do something with my problem? I really can’t think of anything (new Win10 install, new Unity install, problem still remains)

EDIT: I put the pc in single monitor mode and nothing changed, I still get the same errors.

My unity version: 2019.4.12f1 Personal

1 Like
7

You shouldn’t have any errors like this.

Would you mind to create a bug report following the next steps: Unity QA: Building quality with passion

This will help us to check more in-depth about what is happening and solve it accordingly.

Thank you!

8

It seems like it’s gone again. It it happens next time, I will submit a report! Thanks for your help:)

1 Like
9

I believe this is a regression in 2019.4.12, still not corrected in 2019.4.13. I had a thread on this:

I also previously report bug 1284116, which started at the same time and seems potentially related.

1 Like
10

Same thing after upgrading from 2019.4.10f1 to 2019.4.13f1

11

I get same issue, “Invalid editor window” error, try to reset layout to factory settings resulting in “Failed to destroy editor windows: #1” version 2019.4.13f1

12

It is sad and truly unbelievable that these productivity crushing bugs are completely ignored while Unity Technologies prances around with all sorts of flashing marketing and sales and pushing sizzle and wow features when nearly everyone I know that has abandoned and moved on from Unity (triple AAA developers included) have done so because core development grinds to a halt under bugs and broken scenes. The pro devs literally budget out thousands of hours to push through the bugs and broken pieces to get a game out while the smaller devs just get crushed waiting to do simple things like import their assets. It is sad and demoralizing to continue checking in and see there is virtually nothing to be done. Just find another tool or put up with it.

2 Likes
13

If you want to make posts like this, where Unity ignores us common folk, you should pick your battles. Unity fixed this literally yesterday in 2019.4.15.

And you’re saying that this message that was showing up in the console, which had no other impact at all, was a “productivity crushing bug”?

3 Likes
14

I see Wiz’s point of view, I’ve burnt ~2 hours total trying to debug this error on a large project over the past month. I’ve deleted, I’ve recloned from git, I’ve tried disabling stuff along the lines of the Unity suggestions above.

And then today I created a fresh project from Unity Hub just using New → 3D Project and got the same error!

I’m sorry but Unity shouldn’t be releasing software which is this untested, it wastes peoples time.

There should be a test plan before release where someone at Unity hits Create New Project → 3D and see if it works. How that gets past QA is utterly beyond me, it’s the most base level thing to create a new empty 3D project and see the error.

15

I’m facing the very same issue but it’s actually part of another issue.

When I load any project (not a new one) I get this message every time:

The editor layout could not be fully loaded, this can happen when the layout contains EditorWindows not available in this project
UnityEditor.WindowLayout:LoadDefaultWindowPreferences()

Now, that error relates to something went wrong within the Editor layout, so almost everyone says deleting the file located at: \Library\CurrentLayout-default.dwlt or hitting Layout/Revert to factory settings in the Unity editor will solve the issue.

However it doesn’t worked for me, as soon I revert to factory settings the layout, i get the error:

Failed to destroy editor windows: #1
FallbackEditorWindow
UnityEditor.<>c:b__28_0()

So it’s an endless loop every time I open a project.

Also, this bug has brought another big problems to my projects, I have a team of 5 ppl working on collaborate and since I noticed this issue, our project doesn’t work as it should as there are several things that are missing (some references)

At first we had to re-import all the project in order to get back those missing references, luckily enough we pinpoint the folders that were causing the issues (We’re using Photon and a Custom resources folder) but I can vouch that this issue made us lose several hours of work for almost 2 weeks.

We have Unity Plus at our company and also paying seats for collaborate and things like this really makes us want to drop the license.

6587614--748360--Screenshot (4).jpg
6587614--748360--Screenshot (4).jpg1440Ă—900 301 KB
6587614--748363--Screenshot (3).png
6587614--748363--Screenshot (3).png1440Ă—900 197 KB

16

Have you updated to 2019.4.15? I was getting the error in 2019.4.14, but upgrading to 2019.4.15 (along with deleted Library, as recommended) has 100% resolved this for me.

17

No, I haven’t update my version. I can’t.

We are at the middle of a project and as I stated, me and my team are using collab. Can’t force my entire team to update every single time Unity launches a version with some bug.

Considering each new release takes 20-30 mins to fully install with all the components we need… is not viable.

Been using Unity since version 4 but this model of releasing a new LTS version every 3 weeks make me want to throw the computer out of the window with Unity along!

1 Like
18

Well, I don’t think there’s really any option other than either downgrading to 2019.4.11 (before the bug was introduced) or upgrading to 2019.4.15 (where the bug was fixed). If you can’t/won’t upgrade, the I don’t think you have much choice other than just to ignore the error.

Your statement about this having caused other problems with your project seems suspect to me. I don’t know the full details of what went on in this bug, but for me it wasn’t accompanied by any concrete problems, just an annoying console log entry. I’d recommend approaching the other issues independently. Just because two problems started at the same time doesn’t mean they’re related.

19

I just upgraded to 2019.4.16 and get the issue. Was getting it in 2019.4.14 also.

20

Did you fully delete your Library folder after upgrading to 2019.4.16? The bug resolution suggested you’d probably need to do that if simply upgrading doesn’t resolve the issue.