Charles-François Natali <neolo...@free.fr> added the comment: It's a dupe of issue #8426: the Queue isn't full, but the underlying pipe is, so the feeder thread blocks on the write to the pipe (actually when trying to acquire the lock protecting the pipe from concurrent access). Since the children processes join the feeder thread on exit (to make sure all data has been flushed to pipe), they block.
---------- nosy: +neologix resolution: invalid -> duplicate stage: test needed -> committed/rejected status: open -> closed superseder: -> multiprocessing.Queue fails to get() very large objects _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8237> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
