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.

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

Canary [regression] Trouble with close detached window #18497

Closed
Zeroes1 opened this issue Feb 2, 2025 · 2 comments
Closed

Canary [regression] Trouble with close detached window #18497

Zeroes1 opened this issue Feb 2, 2025 · 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

@Zeroes1
Copy link

Zeroes1 commented Feb 2, 2025

Windows Terminal version

terminal-1.23.10311.0

Windows build number

10.0.19045.5371

Other Software

No response

Steps to reproduce

start WT with default config

add new window powershell
detach this window
try to close window

  1. by mouse [click to cross]
  2. alt+f4
  3. ctrl+shift+w

Expected Behavior

terminal-1.23.3461.0 - latest good version

child process (of detached window)
OpenConsole.exe
powershell.exe
closed

Actual Behavior

terminal-1.23.3481.0 - with trouble
...
terminal-1.23.10311.0 - latest canary with trouble

detached window is gone, but if look process manager we see what exist:
OpenConsole.exe
powershell.exe
of detached and closed window :)

If try close detached window with internal command: ( exit [+ enter] for powershell/cmd, F10 for Far Manager)
the associated processes [OpenConsole.exe + powershell.exe/cmd.exe/Far.exe] will be closed normally.

The problem is reproduced 100%.

I think the nature of non-closure of processes is related
#18473

both problem start with terminal-1.23.3481.0 canary

@Zeroes1 Zeroes1 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 Feb 2, 2025
@carlos-zamora
Copy link
Member

Thanks for filing! We're going to mark this as a /duplicate of #18473 since it's related to the non-closure of processes, as you said above.

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 Feb 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

2 participants