starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Terminal unresponsive to keystrokes when outputting large amount of text #10981

New Issue
Closed
opened 2026-01-31 02:35:21 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 02:35:21 +00:00
Owner
Copy Link

Originally created by @cshei on GitHub (Oct 12, 2020).

Environment

Windows build number: 10.0.19042.541
Windows Terminal version (if applicable): 1.4.2652.0 (Preview)

Any other software?  SSH from Windows or WSL

Steps to reproduce

  • SSH to another machine
  • run 'yes' command
  • Press CTRL-C or CTRL-Z

Expected behavior

Terminal output stops shortly after keypress.

Actual behavior

Terminal output continues for an extended period of time (10-30+ seconds). It's worse if you open WSL2 and SSH from there (I just measured it continuing even after 30 seconds and had to close the window because CTRL-C was ineffective), but even launching SSH from PowerShell, it took 9 seconds for the output to stop.

In any Linux terminal, or even the SSH Extension for Chrome, CTRL-C takes less than a second to stop in these cases. I've noticed this behavior since the initial preview releases of Windows Terminal, and it makes using Windows Terminal difficult because if I'm running "emerge" in Gentoo (either in WSL2 or remotely over SSH), the massive amount of compiler commands that get printed cause Windows Terminal to frequently become unresponsive, making it take a really long time to switch TMUX windows away from the emerge or disconnect from the TMUX session.

Running VIM over SSH or mosh also feels sluggish compared to other SSH clients, and when running VIM remotely over mosh in WSL2, I can see the window redrawing when I scroll down with CTRL-F. It shouldn't be an issue of slow hardware, since I see this on both my X1 Carbon gen 7 laptop and my desktop with an i7-8700K and NVIDIA Titan X GPU.

Other than this one issue, Windows Terminal is an awesome piece of software, and I'd definitely use it as my preferred SSH client host if this could be fixed! I'm currently using the SSH and Mosh extensions for Chrome because they do not suffer from this issue.

Originally created by @cshei on GitHub (Oct 12, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.19042.541 Windows Terminal version (if applicable): 1.4.2652.0 (Preview) Any other software? SSH from Windows or WSL ``` # Steps to reproduce * SSH to another machine * run 'yes' command * Press CTRL-C or CTRL-Z # Expected behavior Terminal output stops shortly after keypress. # Actual behavior Terminal output continues for an extended period of time (10-30+ seconds). It's worse if you open WSL2 and SSH from there (I just measured it continuing even after 30 seconds and had to close the window because CTRL-C was ineffective), but even launching SSH from PowerShell, it took 9 seconds for the output to stop. In any Linux terminal, or even the SSH Extension for Chrome, CTRL-C takes less than a second to stop in these cases. I've noticed this behavior since the initial preview releases of Windows Terminal, and it makes using Windows Terminal difficult because if I'm running "emerge" in Gentoo (either in WSL2 or remotely over SSH), the massive amount of compiler commands that get printed cause Windows Terminal to frequently become unresponsive, making it take a really long time to switch TMUX windows away from the emerge or disconnect from the TMUX session. Running VIM over SSH or mosh also feels sluggish compared to other SSH clients, and when running VIM remotely over mosh in WSL2, I can see the window redrawing when I scroll down with CTRL-F. It shouldn't be an issue of slow hardware, since I see this on both my X1 Carbon gen 7 laptop and my desktop with an i7-8700K and NVIDIA Titan X GPU. Other than this one issue, Windows Terminal is an awesome piece of software, and I'd definitely use it as my preferred SSH client host if this could be fixed! I'm currently using the SSH and Mosh extensions for Chrome because they do not suffer from this issue. <!-- What's actually happening? -->
claunia added the Resolution-Duplicate label 2026-01-31 02:35:21 +00:00
claunia commented 2026-01-31 02:35:22 +00:00
Author
Owner
Copy Link

@skyline75489 commented on GitHub (Oct 12, 2020):

I think #198 is the first issue that described the similar issue.

@skyline75489 commented on GitHub (Oct 12, 2020): I think #198 is the first issue that described the similar issue.
claunia commented 2026-01-31 02:35:22 +00:00
Author
Owner
Copy Link

@jdebp commented on GitHub (Oct 13, 2020):

It is ironic that you mention Mosh, because one of the selling points of Mosh has always been that this is a problem in Linux. Specifically, it's a problem when one has SSH or some other remote terminal mechanism in the mix. As such, it is better to reproduce this issue without any involvement of SSH, which only serves to obscure things. But #198 as mentioned already deals in that.

@jdebp commented on GitHub (Oct 13, 2020): It is ironic that you mention Mosh, because one of the selling points of Mosh has always been that this _is_ a problem in Linux. Specifically, it's a problem when one has SSH or some other remote terminal mechanism in the mix. As such, it is better to reproduce this issue _without_ any involvement of SSH, which only serves to obscure things. But #198 as mentioned already deals in that.
claunia commented 2026-01-31 02:35:22 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 16, 2020):

Yep -- there's a couple known issues floating around for this. The one that's had the most research put in, specifically around ^C and SSH, is /dup #6258. Notes in comment https://github.com/microsoft/terminal/issues/6258#issuecomment-649762617.

@DHowett commented on GitHub (Oct 16, 2020): Yep -- there's a couple known issues floating around for this. The one that's had the most research put in, specifically around ^C and SSH, is /dup #6258. Notes in comment https://github.com/microsoft/terminal/issues/6258#issuecomment-649762617.
claunia commented 2026-01-31 02:35:22 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 16, 2020):

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 (Oct 16, 2020): 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!
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 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#10981
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?