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

Bug Report - Process does not die when multiple tabs are open and the close button is pressed. #3977

New Issue
Closed
opened 2026-01-30 23:34:44 +00:00 by claunia · 2 comments
claunia commented 2026-01-30 23:34:44 +00:00
Owner
Copy Link

Originally created by @isubasinghe on GitHub (Sep 22, 2019).

Other

This bug seems to be tied to yarn or react-scripts. I ran a python interpreter in one tab, opened another tab and then closed my terminal. Everything worked as expected. It maybe a bug in yarn or react-scripts, but I am fairly confident that it is not due to step 4. in steps to reproduce. The fact that you have to be out of the tab running the long running process in order to trigger the bug implies to me that this is an issue with terminal.

Environment

Windows build number: 10.0.18362.0 Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable): 0.4.2382

Yarn: 1.17.3 
react-scripts: 3.0.1

Steps to reproduce

  1. Open a terminal
    image
  2. Run yarn start on a CRA Project.
    image
  3. Open a new tab
    image
  4. Navigate to the new tab (this is a requirement)
    image
  5. Click the close button.
  6. Wonder why the terminal is still running
    image

Expected behavior

No matter the amount of open tabs and long running processes, clicking close should kill all running processes in all tabs.

Actual behavior

When a user opens a tab and runs a long running process in it, then opens another tab and then finally closes the terminal, the terminal should kill all running processes.
In my instance I run yarn start with my CRA project in one tab and use the other tab for testing and running git commands. When I click the close button, the terminal does not kill all processes.

Originally created by @isubasinghe on GitHub (Sep 22, 2019). # Other This bug seems to be tied to yarn or react-scripts. I ran a python interpreter in one tab, opened another tab and then closed my terminal. Everything worked as expected. It maybe a bug in yarn or react-scripts, but I am fairly confident that it is not due to step 4. in steps to reproduce. The fact that you have to be out of the tab running the long running process in order to trigger the bug implies to me that this is an issue with terminal. # Environment ```none Windows build number: 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 Windows Terminal version (if applicable): 0.4.2382 Yarn: 1.17.3 react-scripts: 3.0.1 ``` # Steps to reproduce 1. Open a terminal ![image](https://user-images.githubusercontent.com/28187128/65383000-cd6be300-dd51-11e9-838f-1ed666d2f202.png) 2. Run yarn start on a CRA Project. ![image](https://user-images.githubusercontent.com/28187128/65383016-fd1aeb00-dd51-11e9-822b-6ad9656a0273.png) 3. Open a new tab ![image](https://user-images.githubusercontent.com/28187128/65383019-073ce980-dd52-11e9-8c83-338425063184.png) 4. Navigate to the new tab (this is a requirement) ![image](https://user-images.githubusercontent.com/28187128/65383020-0ad07080-dd52-11e9-8aa3-975b9e2bfb3c.png) 5. Click the close button. 6. Wonder why the terminal is still running ![image](https://user-images.githubusercontent.com/28187128/65383029-2b98c600-dd52-11e9-99c8-7731131c9846.png) <!-- A description of how to trigger this bug. --> # Expected behavior No matter the amount of open tabs and long running processes, clicking close should kill all running processes in all tabs. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior When a user opens a tab and runs a long running process in it, then opens another tab and then finally closes the terminal, the terminal should kill all running processes. In my instance I run `yarn start` with my CRA project in one tab and use the other tab for testing and running git commands. When I click the close button, the terminal does not kill all processes.
claunia added the Resolution-Duplicate label 2026-01-30 23:34:44 +00:00
claunia commented 2026-01-30 23:34:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 23, 2019):

/dup #2185

@DHowett-MSFT commented on GitHub (Sep 23, 2019): /dup #2185
claunia commented 2026-01-30 23:34:45 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 23, 2019):

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 (Sep 23, 2019): 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#3977
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?