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 similar to Process, or at the very least an exception to be raised instead of just silently hanging forever. I was able to reproduce this issue both on Linux (Ubuntu 15.04) and Mac OS X. ---------- files: pool_segfault.py messages: 249068 nosy: Jonas Obrist, jnoller, sbt priority: normal severity: normal status: open title: multiprocessing.Pool hangs forever on segfault type: behavior versions: Python 3.4 Added file: http://bugs.python.org/file40243/pool_segfault.py _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue24927> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
