Terminal: reports that some processes continue running even after the tab has been closed

Created on 4 Aug 2019  ·  3Comments  ·  Source: microsoft/terminal

Environment

Windows build number: 10.0.18362.239
Windows Terminal version: 0.3.2142.0
Any other software?
* Clink v0.4.9 [git:2fd2c2] (setup to autoinject, http://mridgers.github.io/clink)
* clink installed by using scoop

Steps to reproduce

  1. Install clink from cmd
    bash $ clink autorun install
  2. Configure terminal default profile to cmd "defaultProfile" : "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}"
  3. Open and close Terminal (UI close button, don't use exit command)

This problem didn't exist in previous public preview build.

Expected behavior

Terminal to exit normally with clink setup.

Actual behavior

Default cmd profile in Terminal with clink setup to autorun, Terminal fails to exit properly and runs in background even after closing.

  • Terminal with clink autorun setup and running normally:
    image

  • Terminal closed normally (UI close button), still running:
    image

When the command exit is used, the terminal exits without the above problem.

Area-Interop Help Wanted Issue-Bug Needs-Tag-Fix Product-Terminal

Most helpful comment

These things should be helped by #2198.

All 3 comments

Same behavior here. Also try opening dynamic port forward - it did stuck after closing terminal and started consuming cpu cycles, but i'm unable to reproduce.

pwsh.exe hangs also

These things should be helped by #2198.

Looks like this is fixed in tag v0.4.2382.0 🎉 by #2198. Closing for now.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

NickITGuy picture NickITGuy  ·  3Comments

waf picture waf  ·  3Comments

ghvanderweg picture ghvanderweg  ·  3Comments

Wid-Mimosa picture Wid-Mimosa  ·  3Comments

warpdesign picture warpdesign  ·  3Comments