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

High CPU utilization #16574

New Issue
Open
opened 2026-01-31 05:16:10 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 05:16:10 +00:00
Owner
Copy Link

Originally created by @KineticTheory on GitHub (Feb 1, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

Microsoft Windows [Version 10.0.19043.1466]

Other Software

No response

Steps to reproduce

  1. Reboot the computer
  2. Start WindowsTerminal and Open a tab for Ubuntu 20.04 (WSL2).
  3. Monitor "Windows Terminal" in Task Manager.
  4. CPU utilization starts at 2-4% and then slowly climbs to exceed 90% even though the terminal is idle and acrylic features are disabled.
  5. This behavior started after installing the January Windows 10 patches.
  6. I only see this behavior when running WSL2 tabs. No processes are using CPU (checked with ps -aux). No other Windows process are consuming significant CPU.

Expected Behavior

CPU utilization for an idle terminal should be very low (certainly less than 5%).

Actual Behavior

If left overnight CPU utilization will exceed 90% of the CPU. Killing WindowsTerminal and restarting it resets CPU utilization to 2-4%, but it will grow over time back to very high values.

wt-about

taskman

In this screenshot, cpu utilization is 28% on a machine with 12 cores (24 hw threads) and the terminal is idle (no running processes).

Originally created by @KineticTheory on GitHub (Feb 1, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number Microsoft Windows [Version 10.0.19043.1466] ### Other Software _No response_ ### Steps to reproduce 1. Reboot the computer 2. Start WindowsTerminal and Open a tab for Ubuntu 20.04 (WSL2). 3. Monitor "Windows Terminal" in Task Manager. 4. CPU utilization starts at 2-4% and then slowly climbs to exceed 90% even though the terminal is idle and acrylic features are disabled. 5. This behavior started after installing the January Windows 10 patches. 6. I only see this behavior when running WSL2 tabs. No processes are using CPU (checked with `ps -aux`). No other Windows process are consuming significant CPU. ### Expected Behavior CPU utilization for an idle terminal should be very low (certainly less than 5%). ### Actual Behavior If left overnight CPU utilization will exceed 90% of the CPU. Killing WindowsTerminal and restarting it resets CPU utilization to 2-4%, but it will grow over time back to very high values. ![wt-about](https://user-images.githubusercontent.com/17579601/152021074-77c61268-d5d4-432b-9462-372a26e84027.jpg) ![taskman](https://user-images.githubusercontent.com/17579601/152021094-03fed545-edb1-411e-907e-b71e09e59b91.jpg) In this screenshot, cpu utilization is 28% on a machine with 12 cores (24 hw threads) and the terminal is idle (no running processes).
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 Needs-Attention Needs-Tag-Fix Needs-Triage Product-WSL Resolution-External
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#16574
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?