Skip to content

Buffer stuck in one of window panes #18880

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
gigit0000 opened this issue May 5, 2025 · 7 comments
Open

Buffer stuck in one of window panes #18880

gigit0000 opened this issue May 5, 2025 · 7 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@gigit0000
Copy link

gigit0000 commented May 5, 2025 •
edited
Loading

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)
@gigit0000 gigit0000 added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels May 5, 2025
@1uigii
Copy link

1uigii commented May 7, 2025 •
edited
Loading

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.

@DHowett
Copy link
Member

DHowett commented 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 DHowett added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label May 7, 2025
@gigit0000
Copy link
Author

@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.

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels May 7, 2025
@DHowett
Copy link
Member

DHowett commented 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 DHowett added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label May 7, 2025
@gigit0000
Copy link
Author

@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.

@microsoft-github-policy-service microsoft-github-policy-service bot removed the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label May 7, 2025
@DHowett
Copy link
Member

DHowett commented May 7, 2025

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

@DHowett DHowett added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Attention The core contributors need to come back around and look at this ASAP. labels May 7, 2025
@gigit0000
Copy link
Author

What more can I share to help clarify the issue?

@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Attention The core contributors need to come back around and look at this ASAP. and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels May 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Attention The core contributors need to come back around and look at this ASAP. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@DHowett @gigit0000 @1uigii