GH-97002: Prevent _PyInterpreterFrame
s from backing more than one PyFrameObject
#97996
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.
There is a nasty situation where a GC collection during
PyFrameObject
allocation could create multiplePyFrameObject
s for the same_PyInterpreterFrame
, which breaks our ownership rules and creates all sorts of opportunities for accessing corrupted memory.If this happens, we just keep the
PyFrameObject
that has already been exposed to user code, and throw away the duplicate.PyFrameObject
s can be created for a single_PyInterpreterFrame
#97002