microsoft / microsoft/terminal

Output slow for 1/2 second, then fast

Open
#20,113 32 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug Needs-Attention Needs-Triage
Dominant language
C++
Stars
105k
Forks
9.6k
Avg merge
3d 17h
Merged PRs (30d)
29

Description

### Windows Terminal version

1.25.2604.02003 (preview) (1.25.923.0) and the previous 1.25 preview

### Windows build number

10.0.26200.8037 (25H2)

### Other Software

TCC shell; v36

### Steps to reproduce

N.B., I have many versions of TCC and WT 1.25, WT 1.24, and WT 1.23 (Store install). I can **only** observe this behavior with WT 1.25 and the newest TCC (v36, now in public beta).

First, wait a while (an hour, several hours, overnight?). When this behavior begins varies and it doesn't seem to have anything to with what **I** do. Then do any of these: press [up] for command history recall, paste into a command line, run a command.

### Expected Behavior

Normal output

### Actual Behavior

If I press [up] a recalled command appears on the command line **slowly**; there's no delay, the characters just stream slowly across the screen. If the recalled command is long enough, after about 1/2 second of slowness, it becomes fast, as usual.

If I paste to a command line the pasted characters appear slowly. If the pasted data is long enough, after about 1/2 second of slowness, it becomes fast, as usual.

If I execute, for example, DIR, the initial output (about 1/2 second, several lines) is slow, thereafter fast.

If I press and hold [up] the result is much like executing DIR ... as I go through the command history output is slow for about 1/2 sec (several lines), then fast.

Once this behavior starts all of the above happen and in several weeks of investigating I haven't found a way to stop it. I must emphasize, there are no outright delays, just slow output followed by normally fast output.

I new instance of the shell (replacing the old one) started with TCC's EXEC command (same ConPty I believe) inherits this problem.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the slow initial output with Windows Terminal 1.25 and TCC v36 after an extended idle period, then compare the same actions in Windows Terminal 1.24 and 1.23. Check command recall, paste, and DIR output separately; done means identifying and correcting the initial half-second slow rendering without changing normal output speed.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, shell
Domain
cli, operating-systems, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.