[3.13] gh-122527: Fix a crash on deallocation of PyStructSequence
(GH-122577)
#122625
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.
The
PyStructSequence
destructor would crash if it was deallocated afterits type's dictionary was cleared by the GC, because it couldn't compute
the "real size" of the instance. This could occur with relatively
straightforward code in the free-threaded build or with a reference
cycle involving the type in the default build, due to differing orders
in which
tp_clear()
was called.Account for the non-sequence fields in
tp_basicsize
and use that,along with
Py_SIZE()
, to compute the "real" size of aPyStructSequence
in the dealloc function. This avoids the accesses tothe type's dictionary during dealloc, which were unsafe.
(cherry picked from commit 4b63cd1)
Co-authored-by: Sam Gross [email protected]