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

Window Resize causing rendering issues #13657

New Issue
Closed
opened 2026-01-31 03:48:34 +00:00 by claunia · 10 comments
claunia commented 2026-01-31 03:48:34 +00:00
Owner
Copy Link

Originally created by @MhammadDayeh on GitHub (Apr 29, 2021).

Windows Terminal version (or Windows build number)

1.7.1033.0

Other Software

No response

Steps to reproduce

I know that this problem has been opened before, and its a duplicate, I am not able to solve the problem, I tried some of the solutions, someone said in another post that changing the historySize from 90000 to 9000, but in this version its already on 9000, I have enabled redraw entire screen option.

To reproduce this problem, I resize the window, and the text goes mayhem, all glitched, this sometimes happens also when I split the powershell in to two (Alt Shift +).

https://user-images.githubusercontent.com/42265793/116483622-7bc5fb80-a898-11eb-85f7-347a4369074d.mp4

Capture

Expected Behavior

Text should not be glitched after resizing.

Actual Behavior

https://user-images.githubusercontent.com/42265793/116483622-7bc5fb80-a898-11eb-85f7-347a4369074d.mp4

Capture

Every time this happens I have to restart the terminal and its been happening ever since I started using windows terminal when its released.

Originally created by @MhammadDayeh on GitHub (Apr 29, 2021). ### Windows Terminal version (or Windows build number) 1.7.1033.0 ### Other Software _No response_ ### Steps to reproduce I know that this problem has been opened before, and its a duplicate, I am not able to solve the problem, I tried some of the solutions, someone said in another post that changing the historySize from 90000 to 9000, but in this version its already on 9000, I have enabled redraw entire screen option. To reproduce this problem, I resize the window, and the text goes mayhem, all glitched, this sometimes happens also when I split the powershell in to two (Alt Shift +). https://user-images.githubusercontent.com/42265793/116483622-7bc5fb80-a898-11eb-85f7-347a4369074d.mp4 ![Capture](https://user-images.githubusercontent.com/42265793/116483710-ab750380-a898-11eb-8fdb-02e999051cad.PNG) ### Expected Behavior Text should not be glitched after resizing. ### Actual Behavior https://user-images.githubusercontent.com/42265793/116483622-7bc5fb80-a898-11eb-85f7-347a4369074d.mp4 ![Capture](https://user-images.githubusercontent.com/42265793/116483710-ab750380-a898-11eb-8fdb-02e999051cad.PNG) Every time this happens I have to restart the terminal and its been happening ever since I started using windows terminal when its released.
claunia added the Area-OutputResolution-DuplicateProduct-Terminal labels 2026-01-31 03:48:34 +00:00
claunia commented 2026-01-31 03:48:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 29, 2021):

Woah, that's way more batty than anything I've seen in the related issues before. Could you share your vim config? That seems like something that's playing into how bad the state of the buffer gets. Also, which version of vim? vim.exe or vim on WSL?

@zadjii-msft commented on GitHub (Apr 29, 2021): Woah, that's way more batty than anything I've seen in the related issues before. Could you share your vim config? That seems like something that's playing into how bad the state of the buffer gets. Also, which version of vim? `vim.exe` or vim on WSL?
claunia commented 2026-01-31 03:48:35 +00:00
Author
Owner
Copy Link

@MhammadDayeh commented on GitHub (Apr 29, 2021):

Hi @zadjii-msft , I dont really think that vim has something to do with this, because this glitch happens without even vim running, in the video I provided I just ran vim as an example of what would happen while doing basic tasks, but I will still provide you with what you are asking for. It is vim 8 for windows not WSL, I will post the vimrc.

@MhammadDayeh commented on GitHub (Apr 29, 2021): Hi @zadjii-msft , I dont really think that vim has something to do with this, because this glitch happens without even vim running, in the video I provided I just ran vim as an example of what would happen while doing basic tasks, but I will still provide you with what you are asking for. It is vim 8 for windows not WSL, I will post the vimrc.
claunia commented 2026-01-31 03:48:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 29, 2021):

The vimrc isn't that important if that's not critical to the repro. If you've got a specific set of steps that'll repro the glitch, that'll work too. I just need something that I can build a test around 😝

@zadjii-msft commented on GitHub (Apr 29, 2021): The vimrc isn't that important if that's not critical to the repro. If you've got a specific set of steps that'll repro the glitch, that'll work too. I just need something that I can build a test around 😝
claunia commented 2026-01-31 03:48:36 +00:00
Author
Owner
Copy Link

@MhammadDayeh commented on GitHub (Apr 29, 2021):

Welp, all what I do is that I literally just resize the window with my mouse, after some time of using the terminal, the glitches happen (sometimes the glitch does not occur until resizing the window more than once), this does not happen at all if the window is not resized. Also this glitch does not always happen, after some search I started to think that the problem is from my end (maybe GPU rendering problem.. idk), but I still would like to know your thoughts. In the meantime, I will try to see if I can notice a specific pattern of steps that causes the issue, I have been using the terminal for some time now and even after resizing multipul times the glitch did not occur yet.

@MhammadDayeh commented on GitHub (Apr 29, 2021): Welp, all what I do is that I literally just resize the window with my mouse, after some time of using the terminal, the glitches happen (sometimes the glitch does not occur until resizing the window more than once), this does not happen at all if the window is not resized. Also this glitch does not always happen, after some search I started to think that the problem is from my end (maybe GPU rendering problem.. idk), but I still would like to know your thoughts. In the meantime, I will try to see if I can notice a specific pattern of steps that causes the issue, I have been using the terminal for some time now and even after resizing multipul times the glitch did not occur yet.
claunia commented 2026-01-31 03:48:36 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Apr 29, 2021):

Maybe I'm not understanding the issue, but this just looks to me like a variant of the "exact wrap" bug (#3088). I can get the same effect by opening vi and resizing the window a bit. If you look at the scrollback at the point it's going to be a mess. Part of the problem is also that conpty doesn't pass through the alt buffer request (#381). If this resizing is happening in a full screen app (i.e. using the alt buffer), then it should never be polluting the scrollback, so you wouldn't typically notice the wrapping problems (except as a brief flash before the screen redraws).

@j4james commented on GitHub (Apr 29, 2021): Maybe I'm not understanding the issue, but this just looks to me like a variant of the "exact wrap" bug (#3088). I can get the same effect by opening vi and resizing the window a bit. If you look at the scrollback at the point it's going to be a mess. Part of the problem is also that conpty doesn't pass through the alt buffer request (#381). If this resizing is happening in a full screen app (i.e. using the alt buffer), then it should never be polluting the scrollback, so you wouldn't typically notice the wrapping problems (except as a brief flash before the screen redraws).
claunia commented 2026-01-31 03:48:36 +00:00
Author
Owner
Copy Link

@MhammadDayeh commented on GitHub (Apr 29, 2021):

@j4james I can see that when vim is running, upon resizing the window I can see the split second of text wrapping (as I refer to as glitching) but then the buffer redraws and everything looks normal. If you see the video I provided, I am not sure why it sometimes happens that the text overlap and create unreadable mess, even after exiting vim, powershell sometimes seem to be glitching, and after pressing enter multipul times the buffer goes back to normal. Today, till now the buffer did not glitch, but it does happen as I managed to record it.

@MhammadDayeh commented on GitHub (Apr 29, 2021): @j4james I can see that when vim is running, upon resizing the window I can see the split second of text wrapping (as I refer to as glitching) but then the buffer redraws and everything looks normal. If you see the video I provided, I am not sure why it sometimes happens that the text overlap and create unreadable mess, even after exiting vim, powershell sometimes seem to be glitching, and after pressing enter multipul times the buffer goes back to normal. Today, till now the buffer did not glitch, but it does happen as I managed to record it.
claunia commented 2026-01-31 03:48:36 +00:00
Author
Owner
Copy Link

@MhammadDayeh commented on GitHub (Apr 29, 2021):

https://user-images.githubusercontent.com/42265793/116607547-314d8900-a943-11eb-837a-07d51b7ee608.mp4

It happened again lol, I was in Vim, I resized my window inside Vim, I exited vim and this happened, I recorded it.

@MhammadDayeh commented on GitHub (Apr 29, 2021): https://user-images.githubusercontent.com/42265793/116607547-314d8900-a943-11eb-837a-07d51b7ee608.mp4 It happened again lol, I was in Vim, I resized my window inside Vim, I exited vim and this happened, I recorded it.
claunia commented 2026-01-31 03:48:36 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 29, 2021):

This definitely looks like the exact wrap bug. Happens most often with vim because it reads and prints back the entire screen buffer (on Windows) which destroys our line wrapping detector.

/dup #3088

@DHowett commented on GitHub (Apr 29, 2021): This definitely looks like the exact wrap bug. Happens most often with vim because it reads and prints back the entire screen buffer (on Windows) which destroys our line wrapping detector. /dup #3088
claunia commented 2026-01-31 03:48:37 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 29, 2021):

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!

@ghost commented on GitHub (Apr 29, 2021): 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!
claunia commented 2026-01-31 03:48:37 +00:00
Author
Owner
Copy Link

@MhammadDayeh commented on GitHub (Apr 29, 2021):

@DHowett Thanks.

@MhammadDayeh commented on GitHub (Apr 29, 2021): @DHowett Thanks.
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 Area-Output Product-Terminal Resolution-Duplicate
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#13657
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?