[issue26659] slice() leaks memory when part of a cycle

Changes by Martin Panter : -- versions: +Python 3.5 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mai

[issue26659] slice() leaks memory when part of a cycle

Roundup Robot added the comment: New changeset 879da9400529 by Benjamin Peterson in branch '2.7': add gc support to slice (closes #26659) https://hg.python.org/cpython/rev/879da9400529 New changeset 9e2176d18965 by Benjamin Peterson in branch '3.5': add gc support to slice (closes #26659) https:

[issue26659] slice() leaks memory when part of a cycle

Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue26659] slice() leaks memory when part of a cycle

Changes by SilentGhost : -- nosy: +benjamin.peterson, georg.brandl, pitrou, yselivanov ___ Python tracker ___ ___ Python-bugs-list mai

[issue26659] slice() leaks memory when part of a cycle

Demur Rumed added the comment: Implementing tp_traverse & tp_clear seems to runs into complications due to slice_cache -- nosy: +Demur Rumed ___ Python tracker ___ _

[issue26659] slice() leaks memory when part of a cycle

New submission from Kevin Modzelewski: The slice type doesn't participate in GC, which means that if you happen to create a cycle involving a slice, that cycle will never get freed. Here's an example: def f(): l = [] l.append(slice(l)) # Will consume memory without bound: while True: