Windows terminal has been terminated when dragging terminal to another display that has different resolution

[KimKiHyuk]

Environment

Windows build number: 10.0.19025.1051
Windows Terminal version (if applicable): 0.6.2951.0

- display1 : 3840 x 2160
- display2: 1920 x 1080

Steps to reproduce

1. launch windows terminal as user mode (bug doesn't occur when running windows terminal as admin)
2. move it to another display

Expected behavior

1. terminal has to be move to a specific display

Actual behavior

1. 'running' icon which looks like blue circle appears
2. terminal is shut down without any message

[cellerich]

Same behavior with me. Even when executed as "Admin".
If the Terminal Window is "PowerShell" then I can move to the other display.
If it is "Ubuntu - WSL" then it will crash

[j4james]

This is probably #3303. Although the fact that is doesn't crash when you're admin is interesting - I've never seen any mention that before.

[KimKiHyuk]

@j4james i think it is related to powershell and cmd. i've just tried open terminal as user mode and close power shell(power shell is default shell for me) and open wsl shell. now i can move terminal to another display. if i have opened power shell or cmd shell and try to move windows terminal to another display, windows terminal die

[j4james]

If you look at #3303 (comment), you'll see that other people have reported similar results with powershell. I'm pretty sure this is the same bug.

[zadjii-msft]

Yea, this is #3303/#2277. I'd bet that the fact it repros in Admin mode is because for some reason, that bug is more or less likely to repro based on the length of the tab title. Really unsure why that is, but in that thread, you'll see that aaaaaaaaaaaaa will repro it consistently, but not longer/shorter titles. It's been my personal hell these last couple weeks 😝

/dup #3303

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!