1.19: "closeOnExit": "always" does not work as expected #20626

Closed
opened 2026-01-31 07:19:28 +00:00 by claunia · 3 comments
Owner

Originally created by @237dmitry on GitHub (Oct 6, 2023).

Windows Terminal version

1.19.2682.0

Windows build number

10.0.22621

Other Software

Any console app.

Steps to reproduce

Kill the application from outside. The tab or panel that the app was running in should automatically close. But that's not true.

Screenshot 2023-10-06 121252

Expected Behavior

Because closeOnExit is set to always, tabs or panels that have terminated applications should always be closed.

In 1.18 preview all worked fine

Actual Behavior

Tabs or panels do not close when the applications running in them are terminated by external commands or actions.

Originally created by @237dmitry on GitHub (Oct 6, 2023). ### Windows Terminal version 1.19.2682.0 ### Windows build number 10.0.22621 ### Other Software Any console app. ### Steps to reproduce Kill the application from outside. The tab or panel that the app was running in should automatically close. But that's not true. ![Screenshot 2023-10-06 121252](https://github.com/microsoft/terminal/assets/78153320/8fba258e-bf73-4fc1-96e3-0524b45e9044) ### Expected Behavior Because `closeOnExit` is set to `always`, tabs or panels that have terminated applications should always be closed. _In 1.18 preview all worked fine_ ### Actual Behavior Tabs or panels do not close when the applications running in them are terminated by external commands or actions.
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 07:19:28 +00:00
Author
Owner

@lhecker commented on GitHub (Oct 6, 2023):

Hey! We've recently already had a report for this issue at #16068. /dup #16068
It was fixed in #16090 and theoretically an update with this should ship next week or so if everything works out fine.

@lhecker commented on GitHub (Oct 6, 2023): Hey! We've recently already had a report for this issue at #16068. /dup #16068 It was fixed in #16090 and theoretically an update with this should ship next week or so if everything works out fine.
Author
Owner

@microsoft-github-policy-service[bot] commented on GitHub (Oct 6, 2023):

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!

@microsoft-github-policy-service[bot] commented on GitHub (Oct 6, 2023): 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! <!-- Policy app identification https://img.shields.io/static/v1?label=PullRequestIssueManagement. -->
Author
Owner

@237dmitry commented on GitHub (Oct 6, 2023):

an update with this should ship next week or so if everything works out fine.

All will be fine

@237dmitry commented on GitHub (Oct 6, 2023): > an update with this should ship next week or so if everything works out fine. All will be fine
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20626