starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Stale output outside the window when switching from fullscreen to windowed mode #21562

New Issue
Closed
opened 2026-01-31 07:48:13 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 07:48:13 +00:00
Owner
Copy Link

Originally created by @tusharsnx on GitHub (Apr 23, 2024).

Windows Terminal version

1.19.10821.0

Windows build number

10.0.22631.0

Other Software

No response

Steps to reproduce

  1. Open Windows Terminal
  2. Go into fullscreen mode with alt+enter
  3. Do another alt+enter to go back to window mode.

Expected Behavior

Everything looks fine, and we're in windowed mode.

Actual Behavior

We're in windowed mode, but the screen still has terminal output stuck in place and that's also outside the app's window frame.

https://github.com/microsoft/terminal/assets/55626797/0b44c73c-065f-428e-b98b-c8c7d6af6019

Originally created by @tusharsnx on GitHub (Apr 23, 2024). ### Windows Terminal version 1.19.10821.0 ### Windows build number 10.0.22631.0 ### Other Software _No response_ ### Steps to reproduce 1. Open Windows Terminal 2. Go into fullscreen mode with alt+enter 3. Do another alt+enter to go back to window mode. ### Expected Behavior Everything looks fine, and we're in windowed mode. ### Actual Behavior We're in windowed mode, but the screen still has terminal output stuck in place and that's also outside the app's window frame. https://github.com/microsoft/terminal/assets/55626797/0b44c73c-065f-428e-b98b-c8c7d6af6019
claunia added the Needs-TriageIssue-Bug labels 2026-01-31 07:48:14 +00:00
claunia commented 2026-01-31 07:48:15 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Apr 23, 2024):

We've seen this issue reported to us before. For instance: #14865
I've also seen the issue with my Nvidia GPU. I think the corruption occurs because DWM (= compositor = blends all windowed applications together into a single image) doesn't get correctly informed about our swap chain resizing. On my Windows 11 26001 build with up to date Nvidia drivers I can't reproduce the issue anymore, but I know that last year it definitely still happened. I'm not sure whether a driver update or Windows fixed it at some point.

@lhecker commented on GitHub (Apr 23, 2024): We've seen this issue reported to us before. For instance: #14865 I've also seen the issue with my Nvidia GPU. I think the corruption occurs because DWM (= compositor = blends all windowed applications together into a single image) doesn't get correctly informed about our swap chain resizing. On my Windows 11 26001 build with up to date Nvidia drivers I can't reproduce the issue anymore, but I know that last year it definitely still happened. I'm not sure whether a driver update or Windows fixed it at some point.
claunia commented 2026-01-31 07:48:15 +00:00
Author
Owner
Copy Link

@tusharsnx commented on GitHub (Apr 23, 2024):

Oh, thanks for pointing me to the original issue.

Could this also happen because we don't resize our swap chains when DWM expects us to do it (when receiving WM_PAINT)? I mean, this is how the terminal looks when we're done processing all the resize events (+ events resulted from that), but the render engine is yet to resize swap chain buffers (I added a breakpoint inside _handleSettingsUpdate):

image

Edit:

I forgot to mention I'm on Intel Iris Xe, so it might very well be a driver or card issue, but I've never seen this issue on other apps.

@tusharsnx commented on GitHub (Apr 23, 2024): Oh, thanks for pointing me to the original issue. Could this also happen because we don't resize our swap chains when DWM expects us to do it (when receiving `WM_PAINT`)? I mean, this is how the terminal looks when we're done processing all the resize events (+ events resulted from that), but the render engine is yet to resize swap chain buffers (I added a breakpoint inside _handleSettingsUpdate): ![image](https://github.com/microsoft/terminal/assets/55626797/0c3a65a0-2308-44aa-8766-fb9949b24953) Edit: I forgot to mention I'm on Intel Iris Xe, so it might very well be a driver or card issue, but I've never seen this issue on other apps.
claunia commented 2026-01-31 07:48:15 +00:00
Author
Owner
Copy Link

@tusharsnx commented on GitHub (Apr 25, 2024):

I'll close this and continue in the original thread.

@tusharsnx commented on GitHub (Apr 25, 2024): I'll close this and continue in the original thread.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Triage
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21562
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?