Author gregory.p.smith
Recipients gregory.p.smith, pitrou
Date 2018-01-17.01:04:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1516151048.85.0.467229070634.issue32576@psf.upfronthosting.co.za>
In-reply-to
Content
As a follow up to https://bugs.python.org/issue14976 which just introduced queue.SimpleQueue:

concurrent.futures.thread currently uses a queue.Queue() from weakref callbacks which could in theory lead to a deadlock when periodic gc triggers a cleanup invalidating some weakrefed objects at an inopportune time while Python code has the queue's lock held.

I don't have a test case proving this (deadlocks are hard).

Switching it to use a SimpleQueue should avoid the problem?

...

This and the C extension module based SimpleQueue would be good to backport to https://pypi.python.org/pypi/futures as well.
History
Date User Action Args
2018-01-17 01:04:09gregory.p.smithsetrecipients: + gregory.p.smith, pitrou
2018-01-17 01:04:08gregory.p.smithsetmessageid: <1516151048.85.0.467229070634.issue32576@psf.upfronthosting.co.za>
2018-01-17 01:04:08gregory.p.smithlinkissue32576 messages
2018-01-17 01:04:07gregory.p.smithcreate