Open transcript opened 6 years ago
Hmmm... might be due to query_per_sequenc
being called via python's subprocess
via a multiprocessing pool. Probably the best way to kill it is to first kill the master python process (using kill -9 <pid of Classify.py>
) and then the spawned processes will finish running in a few seconds and die on their own (or you can kill them manually).
As the title said - I ran Classify.py, only to find that one of my paths (to query_sequences) wasn't correct.
Ctrl + C to interrupt seems to lead to an endless string of processes, apparently running racquire() and self.run(), forcing me to kill the entire window just to escape.
What's going on under the hood that makes this script impossible to terminate once started?