Bug report

Bug description:

The Python C API provides the functionPyGC_Disable() to temporarily disable garbage collection. Calling it causesPyGC_Collect() to become a no-op. So far so good.

Unfortunately, CPython >= 3.12 no longer respects this flag beyond direct calls toPyGC_Collect(). Let's consider, for example, the operationPyErr_CheckSignals() atline 1773. This calls_Py_RunGC, which ignores the GCenabled flag. And thisindeed happens! In fact, I just spent quite a bit of time debugging an issue where the GC was supposed to be disabled for a brief moment, and yet it runs on Python 3.12. (Whether disabling the GC for a brief period of time is a good design pattern is another discussion. I would like to steer the discussion away from this and focus on documented API behavior.)

ThePyErr_CheckSignals() function is called from 135 locations in the CPython codebase including very common ones likePyObject_Str(), so making any fixes in callers of this API does not look feasible.

The flag-ignoring_Py_RunGC() function is only called by two places: besides the mentionedPyErr_CheckSignals(), there is also_Py_HandlePending() inPython/ceval_gil.c.

To restore the documented behavior, I see three options:

• _Py_RunGC() could be modified to exit immediately if theenabled flag is set to zero.
• The implementation of_Py_HandlePending() andPyErr_CheckSignals() could be modified to checkPyGC_IsEnabled() before calling_Py_RunGC().
• Something is setting_PY_GC_SCHEDULED_BIT, and that causes the implementation to enter_Py_RunGC(). I'm not really sure about how that works, but perhaps this flag could be cleared inPyGC_Disable(), and Python could then avoid setting the flag.

(Tagging@pablogsal and@swtaarrs, who commited changes to the relevant code.)

CPython versions tested on:

3.12

Operating systems tested on:

Linux

Linked PRs

• gh-116604: Correctly honor the gc status when calling _Py_RunGC #116628
• [3.12] gh-116604: Correctly honor the gc status when calling _Py_RunGC (GH-116628) #116653
• gh-116604: Fix test_gc on free-threaded build #116662
• gh-116604: Check forgcstate->enabled in _Py_RunGC in free-threaded build #116663