Input freeze on heavy output #19592

Closed
opened 2026-01-31 06:48:12 +00:00 by claunia · 2 comments
Owner

Originally created by @malchera on GitHub (Mar 28, 2023).

Windows Terminal version

1.16.10261.0

Windows build number

10.0.19045.0

Other Software

No response

Steps to reproduce

Produce heavy output (e.g. big compile job, cat on very long file).

Expected Behavior

Responsive Windows Terminal even when heavy output is in place.

Actual Behavior

Windows Terminal becomes unresponsive while there is a heavy output. For example, I am unable to even abort a longer compile job that produces heavy output, i.e. CTRL+{C,D,...} don't work anymore and I have to wait for the output to stop.

Another example is Linux' tmux. If I have a split window open and start compiling on one side and working on the other, as soon as the output starts my session hangs and I am unable to interact with the terminal (till the end of compilation). I tried the same steps using PowerShell, where it works fine.

Originally created by @malchera on GitHub (Mar 28, 2023). ### Windows Terminal version 1.16.10261.0 ### Windows build number 10.0.19045.0 ### Other Software _No response_ ### Steps to reproduce Produce heavy output (e.g. big compile job, `cat` on very long file). ### Expected Behavior Responsive Windows Terminal even when heavy output is in place. ### Actual Behavior Windows Terminal becomes unresponsive while there is a heavy output. For example, I am unable to even abort a longer compile job that produces heavy output, i.e. CTRL+{C,D,...} don't work anymore and I have to wait for the output to stop. Another example is Linux' `tmux`. If I have a split window open and start compiling on one side and working on the other, as soon as the output starts my session hangs and I am unable to interact with the terminal (till the end of compilation). I tried the same steps using PowerShell, where it works fine.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 06:48:12 +00:00
Author
Owner

@carlos-zamora commented on GitHub (Apr 26, 2023):

Thanks for the report! This is a part of a broader class of issues that we're tracking over in #6258. Marking as a /dup of #6258.

@carlos-zamora commented on GitHub (Apr 26, 2023): Thanks for the report! This is a part of a broader class of issues that we're tracking over in #6258. Marking as a /dup of #6258.
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Apr 26, 2023):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Apr 26, 2023): 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#19592