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 Michael.Felt
Recipients Michael.Felt, shihai1991, vstinner
Date 2021-04-01.09:59:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1617271159.96.0.448458221003.issue40092@roundup.psfhosted.org>
In-reply-to
Content
OK: further.

Two options are suggested:

There are different options to solve this issue:

* Reset _tstate_lock before using it... not sure that it's worth it, since we are going to delete the threading.Thread object with its _tstate_lock object anymore. After calling fork, the child process has exactly 1 thread: all other threads have been removed.

* Modify release_sentinel() to not use the lock: avoid PyThread_release_lock() call.

** as to option 1 - it is 'worth it' if it stops the crashes

** This is deeper than I usually go in Python code - but I'll make an effort - help is appreciated.
History
Date User Action Args
2021-04-01 09:59:19Michael.Feltsetrecipients: + Michael.Felt, vstinner, shihai1991
2021-04-01 09:59:19Michael.Feltsetmessageid: <1617271159.96.0.448458221003.issue40092@roundup.psfhosted.org>
2021-04-01 09:59:19Michael.Feltlinkissue40092 messages
2021-04-01 09:59:19Michael.Feltcreate