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

Conhost high CPU usage with Windows Terminal closed #11139

New Issue
Open
opened 2026-01-31 02:39:38 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 02:39:38 +00:00
Owner
Copy Link

Originally created by @imadjamil on GitHub (Oct 23, 2020).

Environment

Microsoft Windows [Version 10.0.19041.572]
Windows Terminal Version: 1.3.2651.0

Steps to reproduce

Close Windows Terminal, wait 5 minutes, then check CPU usage.

Expected behavior

No CPU usage.

Actual behavior

image

Originally created by @imadjamil on GitHub (Oct 23, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 Microsoft Windows [Version 10.0.19041.572] Windows Terminal Version: 1.3.2651.0 # Steps to reproduce Close Windows Terminal, wait 5 minutes, then check CPU usage. <!-- A description of how to trigger this bug. --> # Expected behavior No CPU usage. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior ![image](https://user-images.githubusercontent.com/6026260/96988279-6a381b80-1524-11eb-84dc-b002463d5dea.png) <!-- What's actually happening? -->
claunia added the Issue-BugNeeds-ReproArea-ServerProduct-ConptyPriority-2 labels 2026-01-31 02:39:38 +00:00
claunia commented 2026-01-31 02:39:39 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 23, 2020):

What were you running in the Terminal prior to closing the window?

@zadjii-msft commented on GitHub (Oct 23, 2020): What were you running in the Terminal prior to closing the window?
claunia commented 2026-01-31 02:39:39 +00:00
Author
Owner
Copy Link

@imadjamil commented on GitHub (Oct 23, 2020):

@zadjii-msft I had wsl open with tmux session within. Nothing special. This continues to show the same level of CPU usage even after multiple hours. Is there a way to check what Console Windows Host is doing in the background?

@imadjamil commented on GitHub (Oct 23, 2020): @zadjii-msft I had wsl open with tmux session within. Nothing special. This continues to show the same level of CPU usage even after multiple hours. Is there a way to check what Console Windows Host is doing in the background?
claunia commented 2026-01-31 02:39:39 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 23, 2020):

Hmm. Curious that it's a "Console Window Host", not and "openconsole.exe". What's the commandline of that conhost?

You should be able to create a dump with task manager that we could use to investigate
image

@zadjii-msft commented on GitHub (Oct 23, 2020): Hmm. Curious that it's a "Console Window Host", not and "openconsole.exe". What's the commandline of that conhost? You should be able to create a dump with task manager that we could use to investigate ![image](https://user-images.githubusercontent.com/18356694/97014436-ed02ab80-150f-11eb-8b1a-be443696ceec.png)
claunia commented 2026-01-31 02:39:39 +00:00
Author
Owner
Copy Link

@imadjamil commented on GitHub (Oct 23, 2020):

conhost.zip

@zadjii-msft I have created the dump file. I hope this helps.

@imadjamil commented on GitHub (Oct 23, 2020): [conhost.zip](https://github.com/microsoft/terminal/files/5430140/conhost.zip) @zadjii-msft I have created the dump file. I hope this helps.
claunia commented 2026-01-31 02:39:39 +00:00
Author
Owner
Copy Link

@sna-scourtney commented on GitHub (Apr 30, 2021):

I have a very similar issue, but I have not been able to determine exactly which executable is the problem because it happens only when my screen is locked, and by the time I unlock and open Task Manager, the process has dropped to nearly zero CPU. Where I see the high CPU usage is in the Application History tab of Task Manager, and it only shows "Windows Terminal" with (as far as I know) no additional details available. (Note: I'm a Linux sysadmin and admittedly not as deeply experienced in Windows, so I apologize if there's a Task Manager details setting I have overlooked. I know about showing processes in the current status, but if the App History can do this, I haven't found that setting yet.)

The CPU usage is high enough to spin the fans on my laptop continuously at near-max speed for hours. This happened overnight last night, and the only thing running was one instance of WSL (Ubuntu 20.04) with one shell instance sitting at the bash prompt, no significant background tasks running in Linux.

I came to Github to report a different (unrelated) bug, and stumbled on this one while searching to avoid filing a duplicate on the other. :) So now that I'm aware of this one, I'll try to gather more detailed diagnostic data the next time I observe it.

@sna-scourtney commented on GitHub (Apr 30, 2021): I have a very similar issue, but I have not been able to determine exactly which executable is the problem because it happens only when my screen is locked, and by the time I unlock and open Task Manager, the process has dropped to nearly zero CPU. Where I see the high CPU usage is in the Application History tab of Task Manager, and it only shows "Windows Terminal" with (as far as I know) no additional details available. (Note: I'm a Linux sysadmin and admittedly not as deeply experienced in Windows, so I apologize if there's a Task Manager details setting I have overlooked. I know about showing processes in the _current_ status, but if the App History can do this, I haven't found that setting yet.) The CPU usage is high enough to spin the fans on my laptop continuously at near-max speed for hours. This happened overnight last night, and the only thing running was one instance of WSL (Ubuntu 20.04) with one shell instance sitting at the bash prompt, no significant background tasks running in Linux. I came to Github to report a different (unrelated) bug, and stumbled on this one while searching to avoid filing a duplicate on the other. :) So now that I'm aware of this one, I'll try to gather more detailed diagnostic data the next time I observe it.
claunia commented 2026-01-31 02:39:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 2, 2021):

Thanks for the reports here, and sorry we missed them! We try fairly hard to terminate console sessions when we're done with them, but we do still have some issues here.

I'll put this on our backlog with a "Needs-Repro" tag. It's definitely something that we should fix. I wonder if the console is being starved so that it cannot receive the close event?

@DHowett commented on GitHub (Jul 2, 2021): Thanks for the reports here, and sorry we missed them! We try _fairly_ hard to terminate console sessions when we're done with them, but we do still have some issues here. I'll put this on our backlog with a "Needs-Repro" tag. It's definitely something that we should fix. I wonder if the console is being starved so that it cannot receive the close event?
claunia commented 2026-01-31 02:39:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jul 2, 2021):

If somebody can get me a dump from a "wedged" OpenConsole process -- use OneDrive or Dropbox and send me e-mail to the address on my profile -- that would be so helpful. Please mention this bug number in the title! 😄

@DHowett commented on GitHub (Jul 2, 2021): If somebody can get me a dump from a "wedged" OpenConsole process -- use OneDrive or Dropbox and send me e-mail to the address on my profile -- that would be so helpful. Please mention this bug number in the title! :smile:
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-Server Issue-Bug Needs-Repro Priority-2 Product-Conpty
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#11139
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?