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

Stale python processes are still present after cleaning tasks #149

Closed
jiho opened this issue Apr 13, 2018 · 2 comments
Closed

Stale python processes are still present after cleaning tasks #149

jiho opened this issue Apr 13, 2018 · 2 comments

Comments

@jiho
Copy link
Contributor

jiho commented Apr 13, 2018

Clicking Clean task data on the task page removes the task from the list but leaves the python process runtask.py #tasknumber# running. It should kill it.

@picheral picheral added the feature New functionality label Jul 2, 2018
@picheral picheral added this to the 1.7 (nice to have) milestone Jul 2, 2018
@picheral picheral added the bug label Jul 2, 2018
@picheral picheral removed the bug label Nov 6, 2018
@grololo06 grololo06 changed the title No way to kill a task Stale python processes are still present after cleaning tasks Mar 20, 2020
@grololo06 grololo06 added bug and removed feature New functionality labels Mar 20, 2020
@grololo06
Copy link
Member

I tried today on a long classification, indeed the python subprocess remains active.

@grololo06
Copy link
Member

After code review, it would be unwise to kill the processes. They would leave stale files and others, worst case would be GPU handles. I haven't seen an orphan python process, which would be worse. The processes just die when they try to access their task, which was deleted in DB during the user action "Clean task".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants