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

Windows (probably conhost) sometimes gets stuck. #21912

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

Originally created by @0wwafa on GitHub (Jun 29, 2024).

For a lack of a better description, look at this screenshot:
image

Sometimes, after an out of memory semi-crash, cmd windows remain in this state. If I click on them, nothing happens. (some of them work and open, but others stay in this state) The program run from these windows are still running. It's like the "host" of the window crashed. Obviously if I close them, they close and kill their spawned programs. I wish there was a way to resume them.

Addendum: This happebned to me already a few times in the past. It's like some reference or "father" process is dead and the windows associated with it are unresponsive (as windows, but the processes running inside them are still alive) Also some wsl "bash" windows are affected but no other windows are affected.. so I think it must be some "shell host" or similar process associated with those windows. But I don't know more than that. From past experience I know that if I kill them one by one, every new window (command prompt or bash) work without problems.

I am curious if there is any way to regain control of those windows.

Another example:
image

The two windows on the left are responsive, but the 3 on the right are not. They don't pop up when clicking on them or using alt+tab or task manager.

I am 99% positive that the problem relies in CONHOST.

Originally created by @0wwafa on GitHub (Jun 29, 2024). For a lack of a better description, look at this screenshot: ![image](https://github.com/microsoft/terminal/assets/170285982/9e726eb8-0fac-46ec-8bd7-4e63a3b8def5) Sometimes, after an out of memory semi-crash, cmd windows remain in this state. If I click on them, nothing happens. (some of them work and open, but others stay in this state) The program run from these windows are still running. It's like the "host" of the window crashed. Obviously if I close them, they close and kill their spawned programs. I wish there was a way to resume them. Addendum: This happebned to me already a few times in the past. It's like some reference or "father" process is dead and the windows associated with it are unresponsive (as windows, but the processes running inside them are still alive) Also some wsl "bash" windows are affected but no other windows are affected.. so I think it must be some "shell host" or similar process associated with those windows. But I don't know more than that. From past experience I know that if I kill them one by one, every new window (command prompt or bash) work without problems. I am curious if there is any way to regain control of those windows. Another example: ![image](https://github.com/microsoft/terminal/assets/170285982/6b2c093f-dc2e-454c-af2f-f53b1d529a83) The two windows on the left are responsive, but the 3 on the right are not. They don't pop up when clicking on them or using alt+tab or task manager. I am 99% positive that the problem relies in CONHOST.
claunia added the Product-ConhostNeeds-TriageIssue-BugNeeds-Tag-Fix labels 2026-01-31 07:58:10 +00:00
claunia commented 2026-01-31 07:58:12 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jul 17, 2024):

Thanks for filing! Could you create a dump file using Task Manager for one of these? Also, what version of windows are you on/?

@carlos-zamora commented on GitHub (Jul 17, 2024): Thanks for filing! Could you create a dump file using Task Manager for one of these? Also, what version of windows are you on/?
claunia commented 2026-01-31 07:58:12 +00:00
Author
Owner
Copy Link

@0wwafa commented on GitHub (Jul 18, 2024):

Thanks for filing! Could you create a dump file using Task Manager for one of these? Also, what version of windows are you on/?

hmm I don't have them anymore and it does not happen always... very rarely when memory is full.

About the version, this is something that happened to me in the last years so it affects all versions of windows up until now.
At the moment I am running: Microsoft Windows [Version 10.0.19045.4529]

@0wwafa commented on GitHub (Jul 18, 2024): > Thanks for filing! Could you create a dump file using Task Manager for one of these? Also, what version of windows are you on/? hmm I don't have them anymore and it does not happen always... very rarely when memory is full. About the version, this is something that happened to me in the last years so it affects all versions of windows up until now. At the moment I am running: Microsoft Windows [Version 10.0.19045.4529]
claunia commented 2026-01-31 07:58:13 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Jul 24, 2024):

Ok, we're going to close this then. But if you hit this again, please capture a dump and we'll be happy to reopen it. 😊

@carlos-zamora commented on GitHub (Jul 24, 2024): Ok, we're going to close this then. But if you hit this again, please capture a dump and we'll be happy to reopen it. 😊
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 Issue-Bug Needs-Tag-Fix Needs-Triage Product-Conhost
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#21912
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?