Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

WT doesn't close subprocesses in splitted panes #15801

Closed
h4-h opened this issue Aug 7, 2023 · 2 comments
Closed

WT doesn't close subprocesses in splitted panes #15801

h4-h opened this issue Aug 7, 2023 · 2 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@h4-h
Copy link

h4-h commented Aug 7, 2023

Windows Terminal version

1.17.11461.0

Windows build number

10.0.19044.3086

Other Software

node v18.15.0

Steps to reproduce

  1. open terminal
  2. split pane (shift+alt+-)
  3. run node (npm run dev)
  4. close terminal (alt+f4 or X button)

Expected Behavior

I was expecting subprocesses(in my case it is a node) to close after WT is closed

Actual Behavior

node server still running after closing WT
@h4-h h4-h added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Aug 7, 2023
@zadjii-msft
Copy link
Member

This is wild, this is like, the second report this month. I think this is /dup #15373

@microsoft-github-policy-service
Copy link
Contributor

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 microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Aug 7, 2023
@Jimmaphy Jimmaphy mentioned this issue Feb 18, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zadjii-msft @h4-h