python / python/cpython

PyGILStateEnsure() (Probably) Crashes If Called After Finalization

Open
#124,619 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.12 3.13 3.14 topic-C-API type-bug
Dominant language
Python
Stars
77.2k
Forks
35.9k
PR merge metrics
PR metrics pending

Description

Bug report

Bug description:

I'm pretty sure PyGILState_Ensure() will crash if called after finalization, particularly in the case where the thread doesn't already have a thread state active. I noticed this while looking at the function for something else.

CC @gpshead

CPython versions tested on:

CPython main branch

Operating systems tested on:

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at PyGILState_Ensure() and trace its behavior when called after finalization, especially from a thread without an active thread state. Reproduce the reported crash on CPython main and add or update coverage for the post-finalization call; done means the behavior is defined and no longer crashes.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend-api-design
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.