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

Slow text rendering through SSH and tmux with a lot of text output #4889

New Issue
Closed
opened 2026-01-30 23:59:27 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 23:59:27 +00:00
Owner
Copy Link

Originally created by @NielsH on GitHub (Nov 9, 2019).

Environment

Windows build number: [Version 10.0.19008.1000]
Windows Terminal version (if applicable): 0.6.2951.0

Any other software?
Ubuntu 18.04.3 LTS through WSL v2 / Windows Build 19008

Steps to reproduce

  1. Use ssh to connect to a linux server through the Terminal App running Ubuntu with WSL v2.
  2. Start tmux on the linux server you are connected to through SSH
  3. Run find /
  4. Wait a few seconds (5-10)
  5. Attempt to CTRL+C

Expected behavior

I expect that immediately, or after a few seconds at most, the CTRL+C command interupts the command and scrolling output from the find command in the terminal.

Actual behavior

It seems that the terminal is unable to handle the fast/large amount of text output from the find command. Looking at the time that tmux shows in the bottom-right of the screen, it can be minutes "behind" in rendering the text output.

Other notes:

  • Running in tmux locally, without going through SSH, it takes ~2 seconds for a CTRL+C to come through
  • Running without tmux locally, without going through SSH, CTRL+C is immediate
  • Running without tmux but with SSH, executing a find on a remote linux server, it takes about 5-7 seconds for the CTRL+C to come through.

So it seems only the combination of being connected to another server through SSH, running a tmux there, and then having a lot of text output causes the issue where the terminal is very far (minutes) behind with rendering the text output.

Originally created by @NielsH on GitHub (Nov 9, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: [Version 10.0.19008.1000] Windows Terminal version (if applicable): 0.6.2951.0 Any other software? Ubuntu 18.04.3 LTS through WSL v2 / Windows Build 19008 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Use ssh to connect to a linux server through the Terminal App running Ubuntu with WSL v2. 2. Start tmux on the linux server you are connected to through SSH 3. Run `find /` 4. Wait a few seconds (5-10) 5. Attempt to CTRL+C # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> I expect that immediately, or after a few seconds at most, the CTRL+C command interupts the command and scrolling output from the find command in the terminal. # Actual behavior <!-- What's actually happening? --> It seems that the terminal is unable to handle the fast/large amount of text output from the find command. Looking at the time that tmux shows in the bottom-right of the screen, it can be minutes "behind" in rendering the text output. Other notes: * Running in tmux locally, without going through SSH, it takes ~2 seconds for a CTRL+C to come through * Running without tmux locally, without going through SSH, CTRL+C is immediate * Running without tmux but with SSH, executing a find on a remote linux server, it takes about 5-7 seconds for the CTRL+C to come through. So it seems only the combination of being connected to another server through SSH, running a tmux there, and then having a lot of text output causes the issue where the terminal is very far (minutes) behind with rendering the text output.
claunia added the Resolution-Duplicate label 2026-01-30 23:59:27 +00:00
claunia commented 2026-01-30 23:59:27 +00:00
Author
Owner
Copy Link

@egmontkob commented on GitHub (Nov 9, 2019):

This is probably the same as #3075.

The more of network, ssh, tmux etc. you have, the larger the buffer between find as it emits the data and Terminal as it reads it. Ctrl+C is probably immediately sent to find and it immediately terminates, but there's still a lot of data in these buffers that are yet to be processed by the Terminal.

@egmontkob commented on GitHub (Nov 9, 2019): This is probably the same as #3075. The more of network, ssh, tmux etc. you have, the larger the buffer between `find` as it emits the data and Terminal as it reads it. Ctrl+C is probably immediately sent to `find` and it immediately terminates, but there's still a lot of data in these buffers that are yet to be processed by the Terminal.
claunia commented 2026-01-30 23:59:27 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 11, 2019):

This also has flavors of #1064. Considering this is close enough to the others, let's just call this /dupe of #3075. Thanks!

@zadjii-msft commented on GitHub (Nov 11, 2019): This also has flavors of #1064. Considering this is close enough to the others, let's just call this /dupe of #3075. Thanks!
claunia commented 2026-01-30 23:59:28 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 11, 2019):

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 (Nov 11, 2019): 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#4889
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?