Windows Terminal window becomes unstable after loss/restore of display #5107

Closed
opened 2026-01-31 00:05:11 +00:00 by claunia · 6 comments
Owner

Originally created by @riverar on GitHub (Nov 21, 2019).

Windows 10, 1909 10.0.18363.476
Windows Terminal 0.6.2951.0

Repro steps:

  1. Open Windows Terminal on display 1
  2. Unplug display 1 and replug
  3. Observe:
    • Windows Terminal dimensions have changed
    • Windows Terminal titlebar, control box, and window border are transparent/missing
    • Windows Terminal tab overflow no longer works correctly (i.e. starts overflowing before reaching the end of the titlebar)

This affects users in KVM scenarios.

image

Originally created by @riverar on GitHub (Nov 21, 2019). Windows 10, 1909 10.0.18363.476 Windows Terminal 0.6.2951.0 Repro steps: 1. Open Windows Terminal on display 1 2. Unplug display 1 and replug 3. Observe: * Windows Terminal dimensions have changed * Windows Terminal titlebar, control box, and window border are transparent/missing * Windows Terminal tab overflow no longer works correctly (i.e. starts overflowing before reaching the end of the titlebar) This affects users in KVM scenarios. ![image](https://user-images.githubusercontent.com/475132/69289661-1c978e00-0bb2-11ea-9c78-fd1b978ec962.png)
Author
Owner

@j4james commented on GitHub (Nov 21, 2019):

This might be related to #3446. The exact effect is not the same, but it's also caused by the monitor be unplugged and plugged in again.

@j4james commented on GitHub (Nov 21, 2019): This might be related to #3446. The exact effect is not the same, but it's also caused by the monitor be unplugged and plugged in again.
Author
Owner

@zadjii-msft commented on GitHub (Nov 21, 2019):

I've got a feeling this was maybe improved by #3394, though I can't really be sure. I'll leave this open just in case it does end up being different, though @j4james you're definitely right about the unplugging repro being similar.

🤞 hopefully this just goes away in 0.7 🤞

(I'm putting this on the 1912 milestone to make sure someone follows up after 0.7 is released)

@zadjii-msft commented on GitHub (Nov 21, 2019): I've got a feeling this was maybe improved by #3394, though I can't really be sure. I'll leave this open just in case it does end up being different, though @j4james you're definitely right about the unplugging repro being similar. 🤞 hopefully this just goes away in 0.7 🤞 (I'm putting this on the 1912 milestone to make sure someone follows up after 0.7 is released)
Author
Owner

@riverar commented on GitHub (Nov 21, 2019):

I'm now running a dev build to reproduce, will take a few hours/days to crop back up (if present) as a reboot resolves this issue temporarily.

I suspect this bug is an artifact the longstanding system compositor bug dealing with resize synchronization (@clarkezone has more details).

The system compositor has a workaround (19H1+) to prevent this from happening:
remember

But perhaps it's affecting Windows Terminal in another way.

@riverar commented on GitHub (Nov 21, 2019): I'm now running a dev build to reproduce, will take a few hours/days to crop back up (if present) as a reboot resolves this issue temporarily. I suspect this bug is an artifact the longstanding system compositor bug dealing with resize synchronization (@clarkezone has more details). The system compositor has a workaround (19H1+) to prevent this from happening: ![remember](https://user-images.githubusercontent.com/475132/69362124-c3c40600-0c42-11ea-8465-b6c9cb31a3e3.gif) But perhaps it's affecting Windows Terminal in another way.
Author
Owner

@zadjii-msft commented on GitHub (Dec 4, 2019):

@riverar Is there any chance this was fixed by v0.7 (which should be available now)?

@zadjii-msft commented on GitHub (Dec 4, 2019): @riverar Is there any chance this was fixed by v0.7 (which should be available now)?
Author
Owner

@riverar commented on GitHub (Dec 5, 2019):

@zadjii-msft Am monitoring. If this is the bug I think it is, it will take an indeterminate amount of time to reproduce. Will follow up as soon as I can.

@riverar commented on GitHub (Dec 5, 2019): @zadjii-msft Am monitoring. If this is the bug I think it is, it will take an indeterminate amount of time to reproduce. Will follow up as soon as I can.
Author
Owner

@ghost commented on GitHub (Jan 27, 2020):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jan 27, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#5107