[issue24927] multiprocessing.Pool hangs forever on segfault

Changes by Jonas Obrist : -- resolution: -> duplicate status: open -> closed ___ Python tracker ___

[issue24927] multiprocessing.Pool hangs forever on segfault

Brian Boonstra added the comment: See also issue 22393 -- nosy: +brianboonstra ___ Python tracker ___ ___

[issue24927] multiprocessing.Pool hangs forever on segfault

Changes by Jonas Obrist ojiido...@gmail.com: Added file: http://bugs.python.org/file40248/process_segfault.py ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24927 ___

[issue24927] multiprocessing.Pool hangs forever on segfault

New submission from Jonas Obrist: When using multiprocessing.Pool, if the function run in the pool segfaults, the program will simply hang forever. However when using multiprocessing.Process directly, it runs fine, setting the exitcode to -11 as expected. I would expect the Pool to behave

[issue24927] multiprocessing.Pool hangs forever on segfault

Jonas Obrist added the comment: So the reason this is happening is very simple: When using Pool.apply, the task (function) is sent to the task queue, which is consumed by the worker. At this point the task is in progress. However, the worker dies without being able to finish the task or in