[New-bugs-announce] [issue11663] concurrent.futures (or multiprocessing?) doesn't detect killed processes
report at bugs.python.org
Thu Mar 24 17:09:13 CET 2011
New submission from Antoine Pitrou <pitrou at free.fr>:
If you do:
./python -c "from concurrent.futures import *; from time import *; t = ProcessPoolExecutor(1); t.submit(sleep, 60)"
and then kill the child process, the parent process doesn't notice and waits endlessly for the child to return the results.
I'm using concurrent.futures here but I assume the bug (or limitation) is on the multiprocessing side?
components: Library (Lib)
nosy: asksol, bquinlan, jnoller, pitrou
title: concurrent.futures (or multiprocessing?) doesn't detect killed processes
versions: Python 3.2, Python 3.3
Python tracker <report at bugs.python.org>
More information about the New-bugs-announce