Repository navigation
gh-159739: Break reference cycles involving property objects - #159978
Merged
JelleZijlstra merged 1 commit intoOct 21, 2026
Merged
JelleZijlstra merged 1 commit into
JelleZijlstra merged 1 commit into
Conversation
Backport to 3.15 and 3.14.
JelleZijlstra
added
needs backport to 3.14
|
Thanks @jelle-openai for the PR, and @JelleZijlstra for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14, 3.15. |
|
GH-160014 is a backport of this pull request to the 3.15 branch. |
|
GH-160015 is a backport of this pull request to the 3.14 branch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Break reference cycles involving property objects. The garbage collector can see the property's references to its accessors and name, but its
tp_clearonly clears the docstring. If an unreachable cycle must be broken through one of the other fields,gc.collect()leaves the cycle alive and leaks the objects. You can only exploit this to get a memory leak by setting.__name__or re-calling__init__.Backport to 3.15 and 3.14.