Message 339371 - Python tracker

Message339371

Author	gregory.p.smith
Recipients	Birne94, Connor.Wolf, Giovanni.Bajo, Winterflower, bobbyi, cagney, dan.oreilly, davin, emptysquare, forest_atq, gregory.p.smith, ionelmc, jcea, lesha, neologix, nirai, nirs, ochedru, pitrou, sbt, sdaoden, tshepang, vinay.sajip, vstinner
Date	2019-04-02.22:21:33
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1554243693.76.0.262012241283.issue6721@roundup.psfhosted.org>
In-reply-to

Content
We need a small test case that can reproduce your problem. I believe https://github.com/python/cpython/commit/3b699932e5ac3e76031bbb6d700fbea07492641d to be correct. acquiring locks before fork in the thread doing the forking and releasing them afterwards is always the safe thing to do. Example possibility: Does your code use any C code that forks on its own without properly calling the C Python PyOS_BeforeFork(), PyOS_AfterFork_Parent(), and PyOS_AfterFork_Child() APIs?

Content

We need a small test case that can reproduce your problem.  I believe https://github.com/python/cpython/commit/3b699932e5ac3e76031bbb6d700fbea07492641d to be correct.

acquiring locks before fork in the thread doing the forking and releasing them afterwards is always the safe thing to do.

Example possibility: Does your code use any C code that forks on its own without properly calling the C Python PyOS_BeforeFork(), PyOS_AfterFork_Parent(), and PyOS_AfterFork_Child() APIs?

History
Date	User	Action	Args
2019-04-02 22:21:33	gregory.p.smith	set	recipients: + gregory.p.smith, vinay.sajip, jcea, nirs, pitrou, vstinner, nirai, forest_atq, ionelmc, bobbyi, neologix, Giovanni.Bajo, sdaoden, tshepang, sbt, lesha, emptysquare, dan.oreilly, davin, Connor.Wolf, Winterflower, cagney, Birne94, ochedru
2019-04-02 22:21:33	gregory.p.smith	set	messageid: <1554243693.76.0.262012241283.issue6721@roundup.psfhosted.org>
2019-04-02 22:21:33	gregory.p.smith	link	issue6721 messages
2019-04-02 22:21:33	gregory.p.smith	create