[issue4106] multiprocessing occasionally spits out exception during shutdown
report at bugs.python.org
Wed Jan 19 15:22:10 CET 2011
Jesse Noller <jnoller at gmail.com> added the comment:
On Tue, Jan 18, 2011 at 6:23 PM, Brian Thorne <report at bugs.python.org> wrote:
> Brian Thorne <hardbyte at gmail.com> added the comment:
> With the example script attached I see the exception every time. On Ubuntu 10.10 with Python 2.6
> Since the offending line in multiprocesing/queues.py (233) is a debug statement, just commenting it out seems to stop this exception.
> Looking at the util file shows the logging functions to be all of the form:
> if _logger:
> Could it be possible that after the check the _logger global (or the debug function) is destroyed by the exit handler? Can we convince them to stick around until such a time that they cannot be called?
> Adding a small delay before joining also seems to work, but is ugly. Why should another Process *have* to have a minimum amount of work to not throw an exception?
See http://bugs.python.org/issue9207 - but yes, the problem is that
the VM is nuking our imported modules before all the processes are
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list