This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Jonas Obrist
Recipients Jonas Obrist, jnoller, sbt
Date 2015-08-24.17:05:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440435917.07.0.324379639121.issue24927@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2015-08-24 17:05:17Jonas Obristsetrecipients: + Jonas Obrist, jnoller, sbt
2015-08-24 17:05:17Jonas Obristsetmessageid: <1440435917.07.0.324379639121.issue24927@psf.upfronthosting.co.za>
2015-08-24 17:05:17Jonas Obristlinkissue24927 messages
2015-08-24 17:05:16Jonas Obristcreate