➜

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 mariosoft
Recipients arigo, beazley, benjamin.peterson, brian.curtin, dabeaz, flox, jyasskin, kristjan.jonsson, loewis, mariosoft, navytux, ned.deily, paul.moore, pitrou, python-dev, r.david.murray, rhettinger, ronaldoussoren, sbt, scoder, shihao, techtonik, tim.golden, tim.peters, torsten, vstinner, ysj.ray
Date 2019-10-02.07:20:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1570000826.57.0.693507387503.issue38106@roundup.psfhosted.org>
In-reply-to
Content 
I can confirm that I have the deadlock because of the reason described above. When I change the PyThread_release_lock source locally to signal before releasing the mutex, then my deadlock does not occur anymore. I have tested it on a heave multithreading model.
History
Date User Action Args
2019-10-02 07:20:26mariosoftsetrecipients: + mariosoft, tim.peters, loewis, arigo, rhettinger, beazley, paul.moore, shihao, ronaldoussoren, pitrou, scoder, kristjan.jonsson, vstinner, techtonik, jyasskin, tim.golden, benjamin.peterson, ned.deily, r.david.murray, brian.curtin, flox, dabeaz, torsten, ysj.ray, python-dev, sbt, navytux
2019-10-02 07:20:26mariosoftsetmessageid: <1570000826.57.0.693507387503.issue38106@roundup.psfhosted.org>
2019-10-02 07:20:26mariosoftlinkissue38106 messages
2019-10-02 07:20:26mariosoftcreate