Search Issue Tracker

Fixed in 2022.2.X

Fixed in 2020.3.X, 2021.3.X, 2022.1.X



Found in







Issue ID




Unity Editor crashes when docking one EditorWindow to the side of a docked window

Window management


How to reproduce:
1. Open the user’s attached “” project
2. Select Local/Window1 from the menu to open Window1
3. Select Local/Window2 from the menu to open Window2
4. Dock Window2 to Window1 by dividing it into upper and lower parts
5. Dock Window2 to Window1 by dividing it into left and right
6. Dock Window2 to Window1 by dividing it into upper and lower parts
7. Dock Window2 to the left side of the docked window

Expected result: Window is docked
Actual result: Editor crashes

Reproducible with: 2020.2.0a10, 2020.3.29f1, 2021.2.11f1, 2022.1.0b7, 2022.2.0a4
Not reproducible with: 2019.4.36f1, 2020.2.0a9

- Hard to reproduce on Windows
- Can be reproduced with any window such as Project window, Scene window, etc.

*** First throw call stack:
0 CoreFoundation 0x00007ff81129ff0b __exceptionPreprocess + 242
1 libobjc.A.dylib 0x00007ff811000b9d objc_exception_throw + 48
2 Foundation 0x00007ff812155203 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 267
3 AppKit 0x00007ff813c8afa6 -[NSView setFrameOrigin:] + 1397
4 Unity 0x000000010f1e04d7 -[GUIMetalView setFrameOrigin:] + 39
5 AppKit 0x00007ff813c94f7f -[NSView setFrame:] + 375
6 Unity 0x000000010f1e049c -[GUIMetalView setFrame:] + 60
7 Unity 0x000000010f1d0754 _ZN7GUIView11SetPositionERK5RectTIfE + 564
8 Unity 0x000000010c90db39 _Z44GUIView_CUSTOM_Internal_SetPosition_InjectedP37ScriptingBackendNativeObjectPtrOpaqueRK5RectTIfE + 185
9 ??? 0x00000001705e45fc 0x0 + 6180193788
libc++abi: terminating with uncaught exception of type NSException
Obtained 0 stack frames.
Launching bug reporter
Attribute Qt::AA_EnableHighDpiScaling must be set before QCoreApplication is created.
QObject: Cannot create children for a parent that is in a different thread.
(Parent is QObject(0x600003ca8ac0), parent's thread is QThread(0x600002bf4230), current thread is Thread(0x6000027980f0)

  1. Resolution Note (fix version 2022.2):

    Fixed in 2022.2.0a8

  2. Resolution Note (fix version 2022.1):

    Fixed in 2022.1.0b15

  3. Resolution Note (fix version 2021.3):

    Fixed in 2021.3.2f1

  4. Resolution Note (fix version 2020.3):

    Fixed in 2020.3.35f1

Comments (1)

  1. nicmarxp

    Mar 17, 2022 06:19

    Will this be fixed in 2021.1 LTS? This is such a basic feature and needs to work without crashes.

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.