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

Buffer stuck in one of window panes #23237

New Issue
Closed
opened 2026-01-31 08:36:16 +00:00 by claunia · 12 comments
claunia commented 2026-01-31 08:36:16 +00:00
Owner
Copy Link

Originally created by @gigit0000 on GitHub (May 5, 2025).

Windows Terminal version

1.22.10731.0

Windows build number

19045.5487

Other Software

No response

Steps to reproduce

Image

I'm using 3 panes as shown above. The issue occurs in the upper-right pane only, where I can't scroll up (and the scrollbar disappears) after the print output during SSH is fairly large (over 100 lines). The issue only happens in that pane.

Expected Behavior

I should be able to scroll up.

Actual Behavior

I can't scroll up (and the scrollbar disappears)

Originally created by @gigit0000 on GitHub (May 5, 2025). ### Windows Terminal version 1.22.10731.0 ### Windows build number 19045.5487 ### Other Software _No response_ ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/61d6e832-7dad-4586-a765-727c6f5a97b6) I'm using 3 panes as shown above. The issue occurs in the upper-right pane only, where I can't scroll up (and the scrollbar disappears) **after the print output during SSH is fairly large (over 100 lines)**. The issue only happens in that pane. ### Expected Behavior I should be able to scroll up. ### Actual Behavior I can't scroll up (and the scrollbar disappears)
claunia added the Needs-TriageIssue-BugNeeds-Author-FeedbackNo-Recent-Activity labels 2026-01-31 08:36:16 +00:00
claunia commented 2026-01-31 08:36:18 +00:00
Author
Owner
Copy Link

@1uigii commented on GitHub (May 7, 2025):

I have the exact same problem, but it seems to happen on every pane and randomly even decides to crash the entire terminal.
Windows Terminal version: 1.22.11141.0

When it crashed I was working on a rendering engine that used dx12, after switching the terminal's rendering mode, it resumed for a while until it crashed again. After changing the rendering backend of my engine to vulkan no more crashes appeared.

@1uigii commented on GitHub (May 7, 2025): I have the exact same problem, but it seems to happen on every pane and randomly even decides to crash the entire terminal. Windows Terminal version: 1.22.11141.0 When it crashed I was working on a rendering engine that used dx12, after switching the terminal's rendering mode, it resumed for a while until it crashed again. After changing the rendering backend of my engine to vulkan no more crashes appeared.
claunia commented 2026-01-31 08:36:18 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 7, 2025):

@gigit0000 It looks like you're using a full-screen modal text editor in the pane you have indicated. Usually, those take over scrolling and switch the terminal to an alternate screen with no scrollback.

Can you clarify your issue a bit more? It seems like it might be by design, but we're not totally sure...

When it crashed I was working on a rendering engine that used dx12, after switching the terminal's rendering mode, it resumed for a while until it crashed again. After changing the rendering backend of my engine to vulkan no more crashes appeared.

@1uigii hey this sounds really interesting! It also feels unrelated to this bug report.
Would you mind filing a new issue and including some crash reports as outlined in the troubleshooting tips?

@DHowett commented on GitHub (May 7, 2025): @gigit0000 It looks like you're using a full-screen modal text editor in the pane you have indicated. Usually, those take over scrolling and switch the terminal to an alternate screen with no scrollback. Can you clarify your issue a bit more? It seems like it might be by design, but we're not totally sure... > When it crashed I was working on a rendering engine that used dx12, after switching the terminal's rendering mode, it resumed for a while until it crashed again. After changing the rendering backend of my engine to vulkan no more crashes appeared. @1uigii hey this sounds really interesting! It also feels unrelated to this bug report. Would you mind filing a new issue and including some crash reports as outlined in [the troubleshooting tips](https://github.com/microsoft/terminal/wiki/Troubleshooting-Tips)?
claunia commented 2026-01-31 08:36:18 +00:00
Author
Owner
Copy Link

@gigit0000 commented on GitHub (May 7, 2025):

@DHowett Thanks for your reply. I'm not sure what is "a full-screen modal text editor" (I didn't do any specific setting for any specific pane), but I've experienced this issue for about a year, including in past versions.

Image

What I meant is that the gray handle is gone, so I can't scroll up, and can't see the previous buffer with a key combo either.

@gigit0000 commented on GitHub (May 7, 2025): @DHowett Thanks for your reply. I'm not sure what is "a full-screen modal text editor" (I didn't do any specific setting for any specific pane), but I've experienced this issue for about a year, including in past versions. ![Image](https://github.com/user-attachments/assets/8eb16743-a045-407e-843e-45205311aa34) What I meant is that the gray handle is gone, so I can't scroll up, and can't see the previous buffer with a key combo either.
claunia commented 2026-01-31 08:36:18 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 7, 2025):

I see.

So, in this screenshot:

Image

This is a full screen text editor. It is an application that runs inside a terminal and takes over control of the mouse and scroll bar.

Depending on which editor it is, you may be able to exit it with one of...

  • Ctrl+Q
  • Ctrl+C
  • :q
  • :q!
  • :quit
  • Ctrl+A followed by :quit
@DHowett commented on GitHub (May 7, 2025): I see. So, in this screenshot: ![Image](https://github.com/user-attachments/assets/e3c3642d-05a2-455a-8add-191cf66a6d9d) **This is a full screen text editor.** It is an application that runs inside a terminal and takes over control of the mouse and scroll bar. Depending on which editor it is, you may be able to exit it with one of... - <kbd>Ctrl+Q</kbd> - <kbd>Ctrl+C</kbd> - `:q` - `:q!` - `:quit` - <kbd>Ctrl+A</kbd> followed by `:quit`
claunia commented 2026-01-31 08:36:19 +00:00
Author
Owner
Copy Link

@gigit0000 commented on GitHub (May 7, 2025):

@DHowett The issue I'm referring to isn't related to an editor like vim (I didn't screenshot when the issue occurred. The vim in the screenshot was just a placeholder). After the print output during SSH is fairly large (over 100 lines), the issue only happens in that pane.

@gigit0000 commented on GitHub (May 7, 2025): @DHowett The issue I'm referring to isn't related to an editor like vim (I didn't screenshot when the issue occurred. The vim in the screenshot was just a placeholder). **After the print output during SSH is fairly large (over 100 lines),** the issue only happens in that pane.
claunia commented 2026-01-31 08:36:19 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 7, 2025):

I apologize. We can't assess your issue without an accurate representation of what's happening. :)

@DHowett commented on GitHub (May 7, 2025): I apologize. We can't assess your issue without an accurate representation of what's happening. :)
claunia commented 2026-01-31 08:36:19 +00:00
Author
Owner
Copy Link

@gigit0000 commented on GitHub (May 7, 2025):

What more can I share to help clarify the issue?

@gigit0000 commented on GitHub (May 7, 2025): What more can I share to help clarify the issue?
claunia commented 2026-01-31 08:36:19 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 13, 2025):

We need a pretty specific repro here.

  • what exactly are you running in that page, to get it into that state/?
    • if you're running ssh, which version of ssh?
  • If you repeat exactly those steps in a tab that's not a pane, does that tab get into the same state?
  • when you're in this state, if you hover over the space where the scrollbar is supposed to be, do you see:
Image

My hypothesis is that something in the output of what you're running sets the Terminal into the Alternate Screen Buffer (which has scrolling disabled).

If you're running a WSL in that tab, I'm pretty sure tput reset would get you out of that state (if my hypothesis is correct)

@zadjii-msft commented on GitHub (Aug 13, 2025): We need a pretty specific repro here. * what exactly are you running in that page, to get it into that state/? - if you're running `ssh`, which version of ssh? * If you repeat exactly those steps in a tab that's _not a pane_, does that tab get into the same state? * when you're in this state, if you hover over the space where the scrollbar is supposed to be, do you see: <img width="128" height="520" alt="Image" src="https://github.com/user-attachments/assets/21d678ce-af2f-42df-a115-4f7ae366c252" /> My hypothesis is that something in the output of what you're running sets the Terminal into the Alternate Screen Buffer (which has scrolling disabled). If you're running a WSL in that tab, I'm pretty sure `tput reset` would get you out of that state (if my hypothesis is correct)
claunia commented 2026-01-31 08:36:19 +00:00
Author
Owner
Copy Link

@gigit0000 commented on GitHub (Aug 14, 2025):

Thanks for your feedback.

  • what exactly are you running in that page, to get it into that state/?
    I figured out it isn't related to ssh only, but it occurs in my local too. It also doesn't have to be 3 panes; when a tab has 2 panes, it happens to the right pane only. It just happens while I use the tab for a long period of time (considering the issue happens more with ssh, I figure it would be related to the buffer management).

EDIT: When in 3 panes, it happens much often and quickly.

  • if you're running ssh, which version of ssh?
    Explained above.
  • If you repeat exactly those steps in a tab that's not a pane, does that tab get into the same state?
    Explained above.
  • when you're in this state, if you hover over the space where the scrollbar is supposed to be, do you see:
    Yes but without the handle. That's what I described : https://github.com/microsoft/terminal/issues/18880#issuecomment-2860220589

If you're running a WSL in that tab, I'm pretty sure tput reset would get you out of that state (if my hypothesis is correct)
I'll try out.

@gigit0000 commented on GitHub (Aug 14, 2025): Thanks for your feedback. > > * what exactly are you running in that page, to get it into that state/? I figured out it isn't related to ssh only, but it occurs in my local too. It also doesn't have to be 3 panes; when a tab has 2 panes, it happens to the right pane only. It just happens while I use the tab for a long period of time (considering the issue happens more with ssh, I figure it would be related to the buffer management). EDIT: When in 3 panes, it happens much often and quickly. > > * if you're running `ssh`, which version of ssh? Explained above. > * If you repeat exactly those steps in a tab that's _not a pane_, does that tab get into the same state? Explained above. > * when you're in this state, if you hover over the space where the scrollbar is supposed to be, do you see: Yes but without the handle. That's what I described : https://github.com/microsoft/terminal/issues/18880#issuecomment-2860220589 > If you're running a WSL in that tab, I'm pretty sure `tput reset` would get you out of that state (if my hypothesis is correct) I'll try out.
claunia commented 2026-01-31 08:36:20 +00:00
Author
Owner
Copy Link

@gigit0000 commented on GitHub (Aug 23, 2025):

When the issue occurs, tput reset solves it, but I lose the whole history, unfortunately.
Thank you for your support.

@gigit0000 commented on GitHub (Aug 23, 2025): When the issue occurs, tput reset solves it, but I lose the whole history, unfortunately. Thank you for your support.
claunia commented 2026-01-31 08:36:20 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 24, 2025):

Okay this is great news. What about tput rmcup?

@DHowett commented on GitHub (Aug 24, 2025): Okay this is great news. What about `tput rmcup`?
claunia commented 2026-01-31 08:36:20 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (Sep 1, 2025):

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.

@microsoft-github-policy-service[bot] commented on GitHub (Sep 1, 2025): 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**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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-Author-Feedback Needs-Triage No-Recent-Activity
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#23237
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?