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

Terminal disappears (crashes?) and leaves child processes running (detached from any terminal) #12561

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

Originally created by @NfNitLoop on GitHub (Feb 13, 2021).

Environment

Windows build number: 10.0.19042.0

Windows Terminal version (if applicable): 1.5.10411.0

Any other software?

Steps to reproduce

Unfortunately, I'm not yet able to reproduce this issue, but it's happened twice.

I don't remember the circumstances of the first occurrence, but this time I noticed Terminal had disappeared after waking the machine from sleep. (Update: I just tried putting the computer to sleep and waking it, and it did not trigger this issue.)

I'm happy to try steps to reproduce, but I don't know where to begin here. Are there any logs I should investigate/attach?

Expected behavior

Terminal should not disappear and leave CLI processes running without a terminal.

Actual behavior

I'll have a terminal window open for development, running a couple long-running processes in 2+ tabs. (One is running a web server via cargo run, and the other is running snowpack watch.)

Then, at some point, I'll notice that the Terminal application has stopped and disappeared from my task bar. (It is not on another virtual desktop. It is not listed in the task manager.) I can start a new Terminal without any errors.

However, my old processes are still running ... somewhere? ... without an attached terminal. I can still access the web server that's running locally. If I want to continue development, I need to open task manager and kill the processes so I can run them fresh in a working Terminal.

Originally created by @NfNitLoop on GitHub (Feb 13, 2021). # Environment ```none Windows build number: 10.0.19042.0 Windows Terminal version (if applicable): 1.5.10411.0 Any other software? ``` # Steps to reproduce Unfortunately, I'm not yet able to reproduce this issue, but it's happened [twice]. [twice]: https://twitter.com/NfNitLoop/status/1355276568793235456 I don't remember the circumstances of the [first][twice] occurrence, but this time ~I noticed Terminal had disappeared after waking the machine from sleep. (Update: I just tried putting the computer to sleep and waking it, and it did not trigger this issue.)~ I'm happy to try steps to reproduce, but I don't know where to begin here. Are there any logs I should investigate/attach? # Expected behavior Terminal should not disappear and leave CLI processes running without a terminal. # Actual behavior I'll have a terminal window open for development, running a couple long-running processes in 2+ tabs. (One is running [a web server] via `cargo run`, and the other is running `snowpack watch`.) [a web server]: https://github.com/NfNitLoop/feoblog Then, at some point, I'll notice that the Terminal application has stopped and disappeared from my task bar. (It is not on another virtual desktop. It is not listed in the task manager.) I can start a new Terminal without any errors. However, my old processes are still running ... somewhere? ... without an attached terminal. I can still access the web server that's running locally. If I want to continue development, I need to open task manager and kill the processes so I can run them fresh in a working Terminal.
claunia added the Resolution-Duplicate label 2026-01-31 03:18:48 +00:00
claunia commented 2026-01-31 03:18:48 +00:00
Author
Owner
Copy Link

@luoanni3 commented on GitHub (Mar 4, 2021):

Exactly same here.
This morning I logged into my remote machine and found no Windows Terminal window at all. Only those sub-processes starting in Windows Terminal is still alive in Task Manager yet unreachable.
I have few long-running Windows Terminal windows running, some running only one process, some running multiple processes. The first time happened one month ago but I didn't pay attention to it. The second time I came here and found I'm not the only one...

Windows Terminal version: 1.6.10571.0
Windows version: 10.0.19042.804

@luoanni3 commented on GitHub (Mar 4, 2021): Exactly same here. This morning I logged into my remote machine and found no Windows Terminal window at all. Only those sub-processes starting in Windows Terminal is still alive in Task Manager yet unreachable. I have few long-running Windows Terminal windows running, some running only one process, some running multiple processes. The first time happened one month ago but I didn't pay attention to it. The second time I came here and found I'm not the only one... Windows Terminal version: 1.6.10571.0 Windows version: 10.0.19042.804
claunia commented 2026-01-31 03:18:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 4, 2021):

My working theory is that this is caused by the Store forcibly killing the Terminal to update it. He actually had a similar issue on the previous release, with a similar analysis (https://github.com/microsoft/terminal/issues/7345#issuecomment-677956187). Looks like we're using #6726 to track that issue, so I'm gonna close this as a duplicate.

Thanks!

/duplicate #6726

@zadjii-msft commented on GitHub (Mar 4, 2021): My working theory is that this is caused by the Store forcibly killing the Terminal to update it. He actually had a similar issue on the previous release, with a similar analysis (https://github.com/microsoft/terminal/issues/7345#issuecomment-677956187). Looks like we're using #6726 to track that issue, so I'm gonna close this as a duplicate. Thanks! /duplicate #6726
claunia commented 2026-01-31 03:18:49 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 4, 2021):

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 (Mar 4, 2021): 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 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#12561
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?