-
Notifications
You must be signed in to change notification settings - Fork 6
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
Labels
Milestone
Comments
grololo06
changed the title
No way to kill a task
Stale python processes are still present after cleaning tasks
Mar 20, 2020
I tried today on a long classification, indeed the python subprocess remains active. |
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
Clicking
Clean task data
on the task page removes the task from the list but leaves the python processruntask.py #tasknumber#
running. It should kill it.The text was updated successfully, but these errors were encountered: