[issue22853] Multiprocessing.Queue._feed deadlocks on import

Serhiy Storchaka added the comment: Thank you Florian and Davin for your contribution. -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue22853] Multiprocessing.Queue._feed deadlocks on import

Roundup Robot added the comment: New changeset cf12856bde17 by Serhiy Storchaka in branch '3.4': Issue #22853: Added regression test for using multiprocessing.Queue at import https://hg.python.org/cpython/rev/cf12856bde17 New changeset dcd6d41f2c9a by Serhiy Storchaka in branch 'default': Issue

[issue22853] Multiprocessing.Queue._feed deadlocks on import

Davin Potts added the comment: Corrected patch for 3.4 and default/3.5 -- newly introduced test is now turned on this time and the dangling weak references are properly addressed as well as the reference to Empty. Nastiness. Good save, Serhiy. -- Added file: http://bugs.python.org/f

[issue22853] Multiprocessing.Queue._feed deadlocks on import

Serhiy Storchaka added the comment: As for 3.x, underscored test does not run, and when remove the underscore it runs, but produce a warning (you should run regrtests with -vv to see detailed warnings): $ ./python -m test.regrtest -vv -m '*no_import_lock_contention*' test_multiprocessing_spaw

[issue22853] Multiprocessing.Queue._feed deadlocks on import

Roundup Robot added the comment: New changeset 069c13ca7a70 by Serhiy Storchaka in branch '2.7': Issue #22853: Fixed a deadlock when use multiprocessing.Queue at import time. https://hg.python.org/cpython/rev/069c13ca7a70 -- nosy: +python-dev ___ Pyth

[issue22853] Multiprocessing.Queue._feed deadlocks on import

Serhiy Storchaka added the comment: Oh, right. Harmless. Thanks for all the fish Mark. I meant the bug. -- ___ Python tracker ___ ___

[issue22853] Multiprocessing.Queue._feed deadlocks on import

Mark Lawrence added the comment: That's all we need, harmful patches being committed :) Harmless possibly? -- ___ Python tracker ___

[issue22853] Multiprocessing.Queue._feed deadlocks on import

Serhiy Storchaka added the comment: I'm not sure there is a need to fix this issue. Using multiprocessing Queue at import time looks as yet one way to shoot yourself in the foot. But the patch looks harmful, I'll commit it. -- components: +Library (Lib) stage: patch review -> commit re

[issue22853] Multiprocessing.Queue._feed deadlocks on import

Changes by Serhiy Storchaka : -- assignee: -> serhiy.storchaka nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list ma

[issue22853] Multiprocessing.Queue._feed deadlocks on import

Changes by Davin Potts : Added file: http://bugs.python.org/file38273/issue_22853_only_test_import_lock_in_queue_py34_and_py35.patch ___ Python tracker ___ _

[issue22853] Multiprocessing.Queue._feed deadlocks on import

Davin Potts added the comment: Attaching a patch for 2.7 that applies Florian's fix and provides a test for it as well. Although the issue is not triggered on 3.4 or default (3.5), there is the potential for regression there -- attaching a single patch that works for both 3.4 and 3.5 to provi

[issue22853] Multiprocessing.Queue._feed deadlocks on import

Davin Potts added the comment: Confirmed that the issue can be reproduced under 2.7.9 on OS X 10.10. It is not possible to reproduce the issue with default (3.5) -- taking a look at what's different there, notably the import of is_exiting has moved to the top of the queues module and is no lon

[issue22853] Multiprocessing.Queue._feed deadlocks on import

Mark Lawrence added the comment: @Davin I believe that you're interested in multiprocessing issues. -- nosy: +BreamoreBoy, davin ___ Python tracker ___ __

[issue22853] Multiprocessing.Queue._feed deadlocks on import

Changes by Ned Deily : -- nosy: +sbt ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/ma

[issue22853] Multiprocessing.Queue._feed deadlocks on import

New submission from Florian Finkernagel: If you import a module that creates a multiprocessing.Queue, puts a value, and then waits for to be received again from the queue, you run into a deadlock. The issue is that Queue._feed does 'from .util import is_existing' - which needs the import lock,