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

Considerable input (typing) lag after lots of output #21385

New Issue
Closed
opened 2026-01-31 07:43:10 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 07:43:10 +00:00
Owner
Copy Link

Originally created by @cklutz on GitHub (Mar 11, 2024).

Windows Terminal version

1.19.230925002-preview

Windows build number

10.0.19045.0

Other Software

PowerShell Core 7.4.0

Steps to reproduce

  • In a pane enter some text/commands. Hence, the "typical" input speed. Using movement commands or simply typing random text is OK.
  • In the same pane, run commands that produce "lots of"(!) output. Like repeatedly run large/long builds (msbuild /v:d). It is hard to quantify, but I would say at least couple of 10.000 lines, over the course of a day maybe.
  • Again in the same pane, enter text, move cursor, etc. Performance has degraded considerably. Typing is barely possible, time between hitting the key and visual output are at least a couple of seconds.

When you close the pane and open a new one, (or use a another pane or tab in the same Terminal instance), everything is normal. Only the pane with lots of output is affected it seems.

Note: I have seen this behavior with older versions of Terminal (and PowerShell) and Windows, it is only now that I report it. I'm aware that it might be something environmental or not Terminal related, but I haven't found any existing issue in this or other repos.

Expected Behavior

No recognizable input lag.

Actual Behavior

Considerable input lag.

Originally created by @cklutz on GitHub (Mar 11, 2024). ### Windows Terminal version 1.19.230925002-preview ### Windows build number 10.0.19045.0 ### Other Software PowerShell Core 7.4.0 ### Steps to reproduce * In a pane enter some text/commands. Hence, the "typical" input speed. Using movement commands or simply typing random text is OK. * In the same pane, run commands that produce "lots of"(!) output. Like repeatedly run large/long builds (msbuild /v:d). It is hard to quantify, but I would say at least couple of 10.000 lines, over the course of a day maybe. * Again in the same pane, enter text, move cursor, etc. Performance has degraded considerably. Typing is barely possible, time between hitting the key and visual output are at least a couple of seconds. When you close the pane and open a new one, (or use a another pane or tab in the same Terminal instance), everything is normal. Only the pane with lots of output is affected it seems. Note: I have seen this behavior with older versions of Terminal (and PowerShell) and Windows, it is only now that I report it. I'm aware that it might be something environmental or not Terminal related, but I haven't found any existing issue in this or other repos. ### Expected Behavior No recognizable input lag. ### Actual Behavior Considerable input lag.
claunia commented 2026-01-31 07:43:12 +00:00
Author
Owner
Copy Link

@cklutz commented on GitHub (Mar 14, 2024):

Update: I will leave this here for now, but it looks as if this is really a PowerShell issue. If in the above set, I launch (from inside the "slow shell") CMD.EXE typing feels normal.

If I find more (concrete) evidence, I'll close this one.

@cklutz commented on GitHub (Mar 14, 2024): Update: I will leave this here for now, but it *looks* as if this is really a PowerShell issue. If in the above set, I launch (from inside the "slow shell") `CMD.EXE` typing feels normal. If I find more (concrete) evidence, I'll close this one.
claunia commented 2026-01-31 07:43:13 +00:00
Author
Owner
Copy Link

@pryorda commented on GitHub (Mar 18, 2024):

I have the issue with running wsl and cmd. I dont have the issue in vs-codes terminal

@pryorda commented on GitHub (Mar 18, 2024): I have the issue with running wsl and cmd. I dont have the issue in vs-codes terminal
claunia commented 2026-01-31 07:43:13 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 20, 2024):

Hmm, I'm concerned that there's actually a regression here, especially with the recent comments in #11916 too.

Would any of you be able to install a v1.18.10301.0 build, and double check if 1.18 doesn't show this/? (you should be able to just double-click run windowsterminal.exe in the .zip in that release to run 1.18 side-by-side).

@zadjii-msft commented on GitHub (Mar 20, 2024): Hmm, I'm concerned that there's actually a regression here, especially with the recent comments in #11916 too. Would any of you be able to install a [v1.18.10301.0](https://github.com/microsoft/terminal/releases/tag/v1.18.10301.0) build, and double check if 1.18 _doesn't_ show this/? (you should be able to just double-click run `windowsterminal.exe` in the `.zip` in that release to run 1.18 side-by-side).
claunia commented 2026-01-31 07:43:13 +00:00
Author
Owner
Copy Link

@cklutz commented on GitHub (Mar 21, 2024):

I'd like to that, but I'm no longer at a PC for the next two weeks. I can try it then.

@cklutz commented on GitHub (Mar 21, 2024): I'd like to that, but I'm no longer at a PC for the next two weeks. I can try it then.
claunia commented 2026-01-31 07:43:13 +00:00
Author
Owner
Copy Link

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

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@microsoft-github-policy-service[bot] commented on GitHub (Apr 1, 2024): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**. <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
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 Area-Input Issue-Bug Needs-Author-Feedback Needs-Triage No-Recent-Activity Product-Terminal
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#21385
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?