gh-108724: Fix _PySemaphore_Wait call during thread deletion by colesbury · Pull Request #116483 · python/cpython

colesbury

In general, when `_PyThreadState_GET()` is non-NULL then the current
thread is "attached", but there is a small window during
`PyThreadState_DeleteCurrent()` where that's not true:
tstate_delete_common is called when the thread is detached, but before
current_fast_clear().

This updates _PySemaphore_Wait() to handle that case.

colesbury changed the title ~~gh-116480: Fix _PySemaphore_Wait call during thread deletion~~ gh-108724: Fix _PySemaphore_Wait call during thread deletion

Mar 7, 2024

Co-authored-by: Eric Snow <ericsnowcurrently@gmail.com>

adorilson pushed a commit to adorilson/cpython that referenced this pull request

Mar 25, 2024

…ython#116483)

In general, when `_PyThreadState_GET()` is non-NULL then the current
thread is "attached", but there is a small window during
`PyThreadState_DeleteCurrent()` where that's not true:
tstate_delete_common() is called when the thread is detached, but before
current_fast_clear().

Co-authored-by: Eric Snow <ericsnowcurrently@gmail.com>

diegorusso pushed a commit to diegorusso/cpython that referenced this pull request

Apr 17, 2024

…ython#116483)

In general, when `_PyThreadState_GET()` is non-NULL then the current
thread is "attached", but there is a small window during
`PyThreadState_DeleteCurrent()` where that's not true:
tstate_delete_common() is called when the thread is detached, but before
current_fast_clear().

Co-authored-by: Eric Snow <ericsnowcurrently@gmail.com>