[issue32576] concurrent.futures.thread deadlock due to Queue in weakref callback

[devurandom]

Change by devurandom :


--
nosy: +devurandom

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32576] concurrent.futures.thread deadlock due to Queue in weakref callback

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Perhaps the gemato issue has nothing to do with multiprocessing indeed.  I 
would suggest add some progress logging to your program to see whether/where it 
actually hangs.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32576] concurrent.futures.thread deadlock due to Queue in weakref callback

[Michał Górny]

Michał Górny  added the comment:

Well, according to the reporters disabling GC doesn't help at all. Maybe it's 
another issue.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32576] concurrent.futures.thread deadlock due to Queue in weakref callback

[Ned Deily]

Ned Deily  added the comment:

Yes, backporting all of the required code to earlier releases would be out of 
scope for a maintenance release, particularly at this late stage in the 3.6 
life cycle.  Let's see whether disabling the GC is a sufficient workaround 
until 3.7 is available.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32576] concurrent.futures.thread deadlock due to Queue in weakref callback

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Michał, sorry, I doubt it.  The fix is highly non-trivial as it first requires 
backporting a new feature (see issue14976).  I'm cc'ing the 3.6 branch release 
manager just in case.

If apparently you're witnessing this in controlled situations (the "gemato" 
utility, IIUC?), one workaround would be to disable the cyclic GC (call 
gc.disable()).  If your program doesn't create any cyclic references, or if 
those references don't keep too much memory alive, that would probably work.

--
nosy: +ned.deily

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32576] concurrent.futures.thread deadlock due to Queue in weakref callback

[Michał Górny]

Michał Górny  added the comment:

Could you get this fixed in earlier versions of CPython? Given that 3.7 is not 
yet released, having this broken in 3.5 and 3.6 is highly undesirable. This 
apparently seems to affect our tooling [1] and telling our users to use 3.7 
beta is not an option.

[1]:https://bugs.gentoo.org/647964

--
nosy: +mgorny

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32576] concurrent.futures.thread deadlock due to Queue in weakref callback

[Antoine Pitrou]

Change by Antoine Pitrou :


--
resolution:  -> fixed
stage: patch review -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32576] concurrent.futures.thread deadlock due to Queue in weakref callback

[Antoine Pitrou]

Antoine Pitrou  added the comment:


New changeset ab74504346a6e2569b3255b7b621c589716888c4 by Antoine Pitrou in 
branch 'master':
bpo-32576: use queue.SimpleQueue in critical places (#5216)
https://github.com/python/cpython/commit/ab74504346a6e2569b3255b7b621c589716888c4


--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32576] concurrent.futures.thread deadlock due to Queue in weakref callback

[Antoine Pitrou]

Antoine Pitrou  added the comment:

Thanks for the heads up Mark.  Unfortunately the reproducer script 
https://bugs.python.org/issue21009 needs to hack into Queue.get(), which isn't 
possible for the C-implemented SimpleQueue.

--

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue32576] concurrent.futures.thread deadlock due to Queue in weakref callback

[Gregory P. Smith]

Change by Gregory P. Smith :


--
title: concurrent.futures.thread potential deadlock due to Queue in weakref 
callback -> concurrent.futures.thread deadlock due to Queue in weakref callback

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com