You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Missing Py_CLEAR/Py_VISIT calls for Unpickler.persistent_load_attr and Pickler.persistent_id_attr #130179
I found that Unpickler.persistent_load_attr and Pickler.persistent_id_attr can be set, but never clear. However, I didn't find any uses of them.
Another issue, I found that PDATA_APPEND and PDATA_PUSH may lead to memory leaks if PyErr_NoMemory is raised. What do we do about resources when this happens? I've seen resources get cleared, and sometimes they don't.
changed the title [-]Possible memory leaks in _pickle[/-][+]`_pickle`: Missing `Py_CLEAR/Py_VISIT` calls for `Unpickler.persistent_load_attr` and `Pickler.persistent_id_attr`[/+]on Feb 16, 2025
changed the title [-]`_pickle`: Missing `Py_CLEAR/Py_VISIT` calls for `Unpickler.persistent_load_attr` and `Pickler.persistent_id_attr`[/-][+]Missing `Py_CLEAR/Py_VISIT` calls for `Unpickler.persistent_load_attr` and `Pickler.persistent_id_attr`[/+]on Feb 16, 2025
Activity
Merge branch 'main' into pythongh-130179-pickle-memory-leaks
[-]Possible memory leaks in _pickle[/-][+]`_pickle`: Missing `Py_CLEAR/Py_VISIT` calls for `Unpickler.persistent_load_attr` and `Pickler.persistent_id_attr`[/+][-]`_pickle`: Missing `Py_CLEAR/Py_VISIT` calls for `Unpickler.persistent_load_attr` and `Pickler.persistent_id_attr`[/-][+]Missing `Py_CLEAR/Py_VISIT` calls for `Unpickler.persistent_load_attr` and `Pickler.persistent_id_attr`[/+]gh-130179: Fix `persistent_{id,load}_attr` reference leaks in `_pickl…
pythongh-130179: Fix `persistent_{id,load}_attr` reference leaks in `…
[3.13] gh-130179: Fix `persistent_{id,load}_attr` reference leaks in …