cpython/Misc/NEWS.d/next/C API/2024-05-29-21-05-59.gh-issu...

Fix crash when a thread state that was created by :c:func:`PyGILState_Ensure`
calls a destructor that during :c:func:`PyThreadState_Clear` that
calls back into :c:func:`PyGILState_Ensure` and :c:func:`PyGILState_Release`.
This might occur when in the free-threaded build or when using thread-local
variables whose destructors call :c:func:`PyGILState_Ensure`.
gh-119585: Fix crash involving `PyGILState_Release()` and `PyThreadState_Clear()` (#119753) Make sure that `gilstate_counter` is not zero in when calling `PyThreadState_Clear()`. A destructor called from `PyThreadState_Clear()` may call back into `PyGILState_Ensure()` and `PyGILState_Release()`. If `gilstate_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. 2024-05-31 11:50:52 -03:00			Fix crash when a thread state that was created by :c:func:`PyGILState_Ensure`
			calls a destructor that during :c:func:`PyThreadState_Clear` that
			calls back into :c:func:`PyGILState_Ensure` and :c:func:`PyGILState_Release`.
			`This might occur when in the free-threaded build or when using thread-local`
			variables whose destructors call :c:func:`PyGILState_Ensure`.