This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients Martin Ritter, devin, r.david.murray, rhettinger, sbt
Date 2016-06-30.18:25:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1467311120.13.0.313313923115.issue27422@psf.upfronthosting.co.za>
In-reply-to
Content
It is in-fact problem prone (and not just in Python).  The rule is "thread after you fork, not before".  Otherwise, the locks used by the thread executor will get duplicated across processes.  If one of those processes dies while it has the lock, all of the other processes using that lock will deadlock.
History
Date User Action Args
2016-06-30 18:25:20rhettingersetrecipients: + rhettinger, r.david.murray, devin, sbt, Martin Ritter
2016-06-30 18:25:20rhettingersetmessageid: <1467311120.13.0.313313923115.issue27422@psf.upfronthosting.co.za>
2016-06-30 18:25:20rhettingerlinkissue27422 messages
2016-06-30 18:25:20rhettingercreate