microsoft / microsoft/terminal
Conhost high CPU usage with Windows Terminal closed
Open
Nobody has claimed this yet.
Area-Server
Issue-Bug
Needs-Repro
Priority-2
Product-Conpty
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Begin by reproducing the report with Windows Terminal 1.3.2651.0 on Windows 10.0.19041.572, then trace conhost's CPU activity after the terminal closes. Done means conhost no longer consumes CPU while Windows Terminal is closed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, operating-systems, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100