-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
gh-142975: During GC, mark frozen objects with a merged zero refcount for destruction #143156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
colesbury
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Python/gc_free_threading.c
Outdated
| { | ||
| if (!_PyObject_GC_IS_TRACKED(op)) { | ||
| assert(Py_REFCNT(op) == 0); | ||
| // We have to treat frozen objects as untracked in this function or else |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd add a reference to the issue here. The description there is helpful as well.
// gh-142975: We have to ...
|
Thanks @ZeroIntensity for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14. |
…fcount for destruction (pythonGH-143156) (cherry picked from commit 8611f74e089d9ac9de84dd42be9d251db27889aa) Co-authored-by: Peter Bierma <zintensitydev@gmail.com>
|
GH-143175 is a backport of this pull request to the 3.14 branch. |
validate_refcounts: "tracked objects must have a reference count > 0" #142975