[3.12] gh-119585: Fix crash involving PyGILState_Release()
and PyThreadState_Clear()
(GH-119753)
#119861
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make sure that
gilstate_counter
is not zero in when callingPyThreadState_Clear()
. A destructor called fromPyThreadState_Clear()
may call back intoPyGILState_Ensure()
andPyGILState_Release()
. Ifgilstate_counter
is zero, it will try to create a new thread state before the current active thread state is destroyed, leading to an assertion failure or crash.(cherry picked from commit bcc1be3)