Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity

gh-112529: Don't untrack tuples or dicts with zero refcount (#117370) 

The free-threaded GC sometimes sees objects with zero refcount. This can
happen due to the delay in merging biased reference counting fields,
and, in the future, due to deferred reference counting. We should not
untrack these objects or they will never be collected.

This fixes the refleaks in the free-threaded build.
This commit is contained in:
Sam Gross 2024-03-29 13:33:04 -04:00 committed by GitHub
parent ddf95b5f16
commit f05fb2e65c
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 19 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
Python/gc_free_threading.c
View File

@ -374,7 +374,12 @@ update_refs(const mi_heap_t *heap, const mi_heap_area_t *area,
return true;
}
// Untrack tuples and dicts as necessary in this pass.
Py_ssize_t refcount = Py_REFCNT(op);
_PyObject_ASSERT(op, refcount >= 0);
if (refcount > 0) {
// Untrack tuples and dicts as necessary in this pass, but not objects
// with zero refcount, which we will want to collect.
if (PyTuple_CheckExact(op)) {
_PyTuple_MaybeUntrack(op);
if (!_PyObject_GC_IS_TRACKED(op)) {
@ -389,9 +394,7 @@ update_refs(const mi_heap_t *heap, const mi_heap_area_t *area,
return true;
}
}
Py_ssize_t refcount = Py_REFCNT(op);
_PyObject_ASSERT(op, refcount >= 0);
}
// We repurpose ob_tid to compute "gc_refs", the number of external
// references to the object (i.e., from outside the GC heaps). This means