[3.13] gh-125859: Fix crash when gc.get_objects
is called during GC (GH-125882)
#125921
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes a crash when
gc.get_objects()
orgc.get_referrers()
iscalled during a GC in the free threading build.
Switch to
_PyObjectStack
to avoid corrupting thestruct worklist
linked list maintained by the GC. Also, don't return objects that are frozen
(
gc.freeze()
) or in the process of being collected to more closely matchthe behavior of the default build.
(cherry picked from commit e545ead)
Co-authored-by: Sam Gross [email protected]
gc.get_objects
can corrupt in-progress GC in free threading build #125859