[issue40887] Leaks in new free lists

Change by STINNER Victor : -- pull_requests: +19915 pull_request: https://github.com/python/cpython/pull/20700 ___ Python tracker ___ __

[issue40887] Leaks in new free lists

STINNER Victor added the comment: New changeset 7907f8cbc6923240edb0b5b63adafb871c4c8875 by Victor Stinner in branch 'master': bpo-40887: Fix finalize_interp_clear() for free lists (GH-20698) https://github.com/python/cpython/commit/7907f8cbc6923240edb0b5b63adafb871c4c8875 -- _

[issue40887] Leaks in new free lists

STINNER Victor added the comment: I'm curious about this bug, so I looked at code changes. Before Python 3.6, warnings.c "garbage" is declared as a static variable. It is initialized once but never cleared. In Python 3.7, the variable moved into _PyRuntimeState.gc. In Python 3.8, _PyGC_Fini

[issue40887] Leaks in new free lists

STINNER Victor added the comment: > Lists and tuples sometimes leak (starting 69ac6e58f and later): It's not a regression. It's just that bpo-40521 helped Valgrind to detect such bug :-) I wrote bpo-20698 to fix this issue. I'm also working on a more generic approach to ensure that we don't

[issue40887] Leaks in new free lists

Change by STINNER Victor : -- keywords: +patch pull_requests: +19913 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20698 ___ Python tracker ___ _

[issue40887] Leaks in new free lists

New submission from Stefan Krah : I'm opening a separate issue to prevent #40521 from getting too big. Lists and tuples sometimes leak (starting 69ac6e58f and later): ==1445== 56 bytes in 1 blocks are definitely lost in loss record 1,542 of 4,898 ==1445==at 0x4C2DE56: malloc (vg_replace_m