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

ClosePseudoConsole() leaves lingering conhost.exe processes #5684

New Issue
Closed
opened 2026-01-31 00:19:12 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 00:19:12 +00:00
Owner
Copy Link

Originally created by @krayon007 on GitHub (Dec 24, 2019).

Environment

Windows build number: 10.0.18362.535
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Create PseudoConsole. then associate it with child process (cmd.exe).
Spawn thread to read the output pipe.
At this point, everything about the PseudoConsole appears to work fine. However, when you call ClosePseudoConsole() on the PsuedoConsole handle, it correctly closes the child process, however conhost.exe lingers until the parent process is terminated... If you do this dozens of times, there will be dozens of conhost.exe processes running.

When the child process is terminated, by ClosePseudoConsole(), it does not break the communication pipe. (ie ReadFile does not return). When the process handle for cmd.exe is signaled, I called CancelIoEx() on the pipes, then closed the pipes. This does not seem to have any effect on cleaning up the conhost.exe processes that are lingering. If I spawn dozens of PseudoConsoles in this fashion, and close them in this fashion, only the cmd.exe processes are destroyed. There are still dozens of conhost.exe processes lingering, until the parent process is terminated.

Expected behavior

When calling ClosePseudoConsole(), I expected either a final data frame to be received on the pipe, or the pipe to break when the child process exits. I also expected the conhost.exe process to be destroyed along side the cmd.exe process.

Actual behavior

When calling ClosePseudoConsole(), the cmd.exe process is cleaned up, but the conhost.exe process stays resident until the parent process is terminated.

Originally created by @krayon007 on GitHub (Dec 24, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 ```none Windows build number: 10.0.18362.535 Windows Terminal version (if applicable): Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Create PseudoConsole. then associate it with child process (cmd.exe). Spawn thread to read the output pipe. At this point, everything about the PseudoConsole appears to work fine. However, when you call ClosePseudoConsole() on the PsuedoConsole handle, it correctly closes the child process, however conhost.exe lingers until the parent process is terminated... If you do this dozens of times, there will be dozens of conhost.exe processes running. When the child process is terminated, by ClosePseudoConsole(), it does not break the communication pipe. (ie ReadFile does not return). When the process handle for cmd.exe is signaled, I called CancelIoEx() on the pipes, then closed the pipes. This does not seem to have any effect on cleaning up the conhost.exe processes that are lingering. If I spawn dozens of PseudoConsoles in this fashion, and close them in this fashion, only the cmd.exe processes are destroyed. There are still dozens of conhost.exe processes lingering, until the parent process is terminated. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> When calling ClosePseudoConsole(), I expected either a final data frame to be received on the pipe, or the pipe to break when the child process exits. I also expected the conhost.exe process to be destroyed along side the cmd.exe process. # Actual behavior <!-- What's actually happening? --> When calling ClosePseudoConsole(), the cmd.exe process is cleaned up, but the conhost.exe process stays resident until the parent process is terminated.
claunia added the Resolution-DuplicateProduct-Conpty labels 2026-01-31 00:19:13 +00:00
claunia commented 2026-01-31 00:19:13 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Jan 2, 2020):

This is going to be related to #1810.

@miniksa commented on GitHub (Jan 2, 2020): This is going to be related to #1810.
claunia commented 2026-01-31 00:19:14 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Jan 2, 2020):

/dup #1810

@miniksa commented on GitHub (Jan 2, 2020): /dup #1810
claunia commented 2026-01-31 00:19:14 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jan 2, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Jan 2, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Product-Conpty Resolution-Duplicate
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#5684
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?