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

Unexpected behavior of closeOnExit #5432

New Issue
Open
opened 2026-01-31 00:13:11 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 00:13:11 +00:00
Owner
Copy Link

Originally created by @tomasr on GitHub (Dec 6, 2019).

Originally assigned to: @DHowett on GitHub.

Environment

Windows 10 version 10.0.18362.0
Windows Terminal 0.7.3291.0
PowerShell Core version 6.2.3

Steps to reproduce

Created a manual profile for PowerShell Core (as an automatic profile won't get added when it's installed as a dotnet global tool), like this:

    {
      "guid": "{1ba0ecbe-ee5f-4f20-80fc-c7f3376445ca}",
      "name": "PowerShell Core",
      "commandline": "%USERPROFILE%\\.dotnet\\tools\\pwsh.exe",
      "startingDirectory": "%USERPROFILE%",
      "hidden": false,
      "fontFace": "Cascadia Mono PL",
      "fontSize": 13,
      "colorScheme": "Gruvbox Dark"
    }

Create a new PowerShell Core window, then run a native command (.exe) that takes a bit of time to run and then immediately hit Ctrl+C.

In my case, I've tested this running both java applications as well as kubectl get pods --all-namespaces for my kubernetes cluster.

Expected behavior

I'd expect the native application to handle the Ctrl+C, terminate, and get back to the PowerShell Core prompt.

Actual behavior

The entire Windows Terminal tab is getting killed, as if the shell had been terminated.

What appears to be going on here is related to the closeOnExit setting. My original profile used the default value for this, and apparently, Windows Terminal is mistaking the child process terminating due to Ctrl+C as the PowerShell Core shell terminating, so it's killing the tab window.

Setting closeOnExit: false seems to work around this, and lets the tab open, but the default behavior is very surprising, and seems like a bug tracking which process terminated.

Originally created by @tomasr on GitHub (Dec 6, 2019). Originally assigned to: @DHowett on GitHub. # Environment Windows 10 version 10.0.18362.0 Windows Terminal 0.7.3291.0 PowerShell Core version 6.2.3 # Steps to reproduce Created a manual profile for PowerShell Core (as an automatic profile won't get added when it's installed as a dotnet global tool), like this: ```json { "guid": "{1ba0ecbe-ee5f-4f20-80fc-c7f3376445ca}", "name": "PowerShell Core", "commandline": "%USERPROFILE%\\.dotnet\\tools\\pwsh.exe", "startingDirectory": "%USERPROFILE%", "hidden": false, "fontFace": "Cascadia Mono PL", "fontSize": 13, "colorScheme": "Gruvbox Dark" } ``` Create a new PowerShell Core window, then run a native command (.exe) that takes a bit of time to run and then immediately hit `Ctrl+C`. In my case, I've tested this running both java applications as well as `kubectl get pods --all-namespaces` for my kubernetes cluster. # Expected behavior I'd expect the native application to handle the `Ctrl+C`, terminate, and get back to the PowerShell Core prompt. # Actual behavior The entire Windows Terminal tab is getting killed, as if the shell had been terminated. What appears to be going on here is related to the `closeOnExit` setting. My original profile used the default value for this, and apparently, Windows Terminal is mistaking the child process terminating due to `Ctrl+C` as the PowerShell Core shell terminating, so it's killing the tab window. Setting `closeOnExit: false` seems to work around this, and lets the tab open, but the default behavior is very surprising, and seems like a bug tracking which process terminated.
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 Area-TerminalConnection Issue-Bug Needs-Tag-Fix Product-Powershell Tracking-External
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#5432
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?