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

Terminal process remains on background after exiting it #2258

Closed
hwooo opened this issue Aug 5, 2019 · 2 comments
Closed

Terminal process remains on background after exiting it #2258

hwooo opened this issue Aug 5, 2019 · 2 comments
Labels
Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@hwooo
Copy link

hwooo commented Aug 5, 2019

Environment

Windows build number: [run "ver" at a command prompt] 10.0.18362.267
Windows Terminal version (if applicable): v0.3.2142.0

Any other software? No

Steps to reproduce

Error 1: CMD

  1. Open Windows Terminal
  2. Open CMD tab
  3. Close Terminal

Error 2: Ubuntu

  1. Open Windows Terminal
  2. Open Ubuntu tab
  3. Input any command
  4. Close Terminal

Actual behavior

Error 1: CMD

pic1

Error 2: Ubuntu

pic3

Terminal process remains on background and especially it occupies CPU resources excessively when after exiting terminal used as CMD.

When I use only PowerShell, terminal process disappears from background process list immediately after exiting terminal.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Aug 5, 2019
@hwooo hwooo changed the title Terminal process remains on background Terminal process remains on background after exiting it Aug 5, 2019
@dynalz
Copy link

dynalz commented Aug 12, 2019

Indeed this happens to me aswell.
Some scripts I have on python have been running on background without my knowledge after closing out Windows Terminal. I saw them accidentally because logs were being written and I happen to notice.

Quite easy to test running any background process that opens up a port (node API or frontend web dev), in my case, after closing windows terminal http://localhost:8080/ keeps being accessible due to process never shutting down

@ghost ghost added In-PR This issue has a related PR and removed In-PR This issue has a related PR labels Aug 15, 2019
@DHowett-MSFT
Copy link
Contributor

This looks like another shade of #2232.

@DHowett-MSFT DHowett-MSFT added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Aug 16, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Aug 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting 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

3 participants