starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

child bash processes are left running after Windows Store updates Terminal and closes it #15736

New Issue
Closed
opened 2026-01-31 04:47:00 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 04:47:00 +00:00
Owner
Copy Link

Originally created by @chrisan on GitHub (Oct 29, 2021).

Windows Terminal version (or Windows build number)

10.0.19043.1288

Other Software

Ubuntu 20.04.2 LTS
GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)

Steps to reproduce

  1. Launch the most recent Windows Store version of Microsoft Terminal
  2. Use Ubuntu 20 LTS
  3. Start a bash process such as a local development server (in php or node)
  4. Begin your normal work
  5. Each end of day after work leave your terminal running but allow computer to go to sleep
  6. Each morning wake up your computer resume work with Terminal behaving as expect
  7. Wait for the next Windows Store update to Terminal
  8. Observe your Terminal has been closed randomly one morning after waking the computer but your local dev servers are still accessible in the browser and the only way to shut down these servers is to open Task manager and kill instances of bash

Expected Behavior

I expect when Terminal is shutdown by Windows Store automatic updates that all child processes are also shutdown

Actual Behavior

Child processes are not shutdown when Terminal is shutdown for a Windows Store update

This is not a new issue to the latest Windows Terminal, it's been happening for probably as long as I've been using Terminal > 1yr

Originally created by @chrisan on GitHub (Oct 29, 2021). ### Windows Terminal version (or Windows build number) 10.0.19043.1288 ### Other Software Ubuntu 20.04.2 LTS GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu) ### Steps to reproduce 1. Launch the most recent Windows Store version of Microsoft Terminal 2. Use Ubuntu 20 LTS 3. Start a bash process such as a local development server (in php or node) 4. Begin your normal work 5. Each end of day after work leave your terminal running but allow computer to go to sleep 6. Each morning wake up your computer resume work with Terminal behaving as expect 4. Wait for the next Windows Store update to Terminal 5. Observe your Terminal has been closed randomly one morning after waking the computer but your local dev servers are still accessible in the browser and the only way to shut down these servers is to open Task manager and kill instances of bash ### Expected Behavior I expect when Terminal is shutdown by Windows Store automatic updates that all child processes are also shutdown ### Actual Behavior Child processes are not shutdown when Terminal is shutdown for a Windows Store update This is not a new issue to the latest Windows Terminal, it's been happening for probably as long as I've been using Terminal > 1yr
claunia added the Resolution-Duplicate label 2026-01-31 04:47:00 +00:00
claunia commented 2026-01-31 04:47:02 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Oct 30, 2021):

See issues #3915 and #6726.

@j4james commented on GitHub (Oct 30, 2021): See issues #3915 and #6726.
claunia commented 2026-01-31 04:47:02 +00:00
Author
Owner
Copy Link

@chrisan commented on GitHub (Nov 1, 2021):

Hi @j4james these seem to be about preventing auto updates entirely? I don't mind the auto update (even if it does mean I have to restart any processes) this was more specifically about all those processes are just detached and left running when the Store performs the update

For example when I close Terminal, all child processes are killed. When Store closes Terminal for an update, no child processes are killed - just detached

@chrisan commented on GitHub (Nov 1, 2021): Hi @j4james these seem to be about preventing auto updates entirely? I don't mind the auto update (even if it does mean I have to restart any processes) this was more specifically about all those processes are just detached and left running when the Store performs the update For example when I close Terminal, all child processes are killed. When Store closes Terminal for an update, no child processes are killed - just detached
claunia commented 2026-01-31 04:47:02 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 1, 2021):

This sounds like the discussion in #9914 which actually didn't end up getting triaged before (my bad). @chrisan can you follow up in that thread? Specifically, I'm interested if this consistently happens with the children of one particular type of shell? For example, does this always happen with WSL processes, or does it happen with children running in powershell.exe too?

Thanks!

/dup #9914

@zadjii-msft commented on GitHub (Nov 1, 2021): This sounds like the discussion in #9914 which actually didn't end up getting triaged before (my bad). @chrisan can you follow up in that thread? Specifically, I'm interested if this consistently happens with the children of one particular type of shell? For example, does this always happen with WSL processes, or does it happen with children running in `powershell.exe` too? Thanks! /dup #9914
claunia commented 2026-01-31 04:47:03 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 1, 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 (Nov 1, 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#15736
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?