Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[3.12] gh-104341: Call _PyEval_ReleaseLock() with NULL When Finalizing the Current Thread (gh-105109) #105209

Merged
merged 1 commit into from
Jun 1, 2023
Merged

[3.12] gh-104341: Call _PyEval_ReleaseLock() with NULL When Finalizing the Current Thread (gh-105109) #105209

merged 1 commit into from
Jun 1, 2023

Commits on Jun 1, 2023

  1. pythongh-104341: Call _PyEval_ReleaseLock() with NULL When Finalizing… 

    … the Current Thread (pythongh-105109)

This avoids the problematic race in drop_gil() by skipping the FORCE_SWITCHING code there for finalizing threads.

(The idea for this approach came out of discussions with @markshannon.)
(cherry picked from commit 3698fda)

Co-authored-by: Eric Snow <ericsnowcurrently@gmail.com>
    @ericsnowcurrently @miss-islington
    ericsnowcurrently authored and miss-islington committed Jun 1, 2023
    Configuration menu
    Copy the full SHA
    d7f46a8 View commit details
    Browse the repository at this point in the history