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 gdb
Recipients gdb
Date 2010-07-08.20:00:41
SpamBayes Score 3.0284439e-06
Marked as misclassified No
Message-id <>
I have recently begun using multiprocessing for a variety of batch
jobs.  It's a great library, and it's been quite useful.  However, I have been bitten several times by situations where a worker process in a Pool will unexpectedly die, leaving multiprocessing hanging in a wait.  A simple example of this is produced by the following:
#!/usr/bin/env python
import multiprocessing, sys
def foo(x):
multiprocessing.Pool(1).apply(foo, [1])
The child will exit and the parent will hang forever.  A similar occurrence happens if one pushes C-c while a child process is running (this special case is noted in or killed by a signal.

Attached is a patch to handle unexpected terminations of children
processes and prevent the parent process from hanging.  A test case is included.  (Developed and tested on 64-bit Ubuntu.)  Please let me know what you think.  Thanks!
Date User Action Args
2010-07-08 20:00:51gdbsetrecipients: + gdb
2010-07-08 20:00:51gdbsetmessageid: <>
2010-07-08 20:00:44gdblinkissue9205 messages
2010-07-08 20:00:44gdbcreate