terminal: Terminal crashes when dragged to another monitor
Environment
Windows build number: Microsoft Windows [Version 10.0.18362.418]
Windows Terminal version (if applicable): 0.6.2951.0
Steps to reproduce
- Open Windows Terminal with “only one tab open”
- Drag to another monitor with a lower resolution (from 2160p to 1080p)
Expected behavior
Terminal is dragged onto another monitor
Actual behavior
It crashes. Funny thing: The terminal doesn’t crash when I have more than one tab open.
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 37
- Comments: 47 (16 by maintainers)
Commits related to this issue
- Well, the RelativePanel seems to indicate that it's not just the MaxWidth call that's the problem here For tagging purposes: #3303. All the other branches aren't pushed, but this one is the latest ... — committed to microsoft/terminal by zadjii-msft 5 years ago
- Merge remote-tracking branch 'origin/master' into dev/migrie/b/3303-by-merging-3347 I was really hoping that this would be a magic solution to #3303, but it isn't. It suffers the same E_LAYOUTCYC... — committed to microsoft/terminal by zadjii-msft 5 years ago
- What if we just didn't have a drag bar at all? Answer: We'd still get E_LAYOUTCYCLEs. See #3303 I'm giving up (for real) for now. — committed to microsoft/terminal by zadjii-msft 5 years ago
- Update to the latest MUX prerelease (#3832) ## Summary of the Pull Request Updates MUX to the latest pre-release version. This prerelease has a fix for a certain `E_LAYOUTCYCLE` bug in the TabView... — committed to microsoft/terminal by zadjii-msft 5 years ago
- Update to the latest MUX prerelease (#3832) Updates MUX to the latest pre-release version. This prerelease has a fix for a certain `E_LAYOUTCYCLE` bug in the TabView that was causing an untold number... — committed to microsoft/terminal by zadjii-msft 5 years ago
Just hit this bug. The multiple tabs with cmd workaround is the only thing that works for me.
Hey everyone, just an update here:
I’ve dug real deep into XAML over the last week, and working with @teap, we were able to find that the source of the
E_LAYOUTCYCLEwasn’t coming from the Windows Terminal code, it was coming from theTabViewcode itself. Fortunately, @teap has whipped up a fix for us, which should be available on the next update ofMicrosoft.UI.Xaml🎉.At the time of writing it’s unclear when we’ll ingest that update and push an update to the store. We’ll keep you posted in this thread when we know more. Thanks all for help with getting repro steps found!
For me the multiple tabs work around only works if one of the tabs is CMD
edit: Also noticed it’s only when moving from my laptop screen(4k) to an external monitor(1080p). Moving between my external monitors seems fine. Maybe due to them using different graphic cards?
It has nothing to do with the drag … the same crash behaviour is exhibited if you use the windows + arrow keys
welp. That’s insane, but it works. I’ll dig in farther in the morning.
My notes: Win-Shift-Left and Win-Shift-Right work fine, its just when “dragging” the window.
I’m having the same issue on my setup. Two tabs workaround doesn’t help.
Primary monitor is 2K at 125% and other monitors are 1080p at 100%. The app crashes as soon as I move it from the primary monitor to the others.
Okay so it’s even more challenging that just dragging it to another display while it’s starting up. It specifically crashes if the title is changing when you drag it to the other display. I’m not sure if it has to change exactly during the drag, or how it’s related, but now that I have a little script repros this consistently, I can investigate more.
I can consistently reproduce it when I set Ubuntu-18.04 as the default profile, it does not happen when openning Windows PowerShell or cmd.
Then I also have to quickly drag Terminal to another monitor, while it is still loading Ubuntu, if I wait a few seconds for the command prompt to be ready, then I can safely move Terminal to another monitor without it crashing.
which is 100% what I said.
Hi, I just sent a feedback using the Feedback Hub. Thanks everyone for more details.
https://aka.ms/AA6e9sl
https://aka.ms/AA6eg31