[issue13199] slice_richcompare() might leak an object in rare cases

Roundup Robot added the comment: New changeset 53c87a0275ab by Benjamin Peterson in branch '3.2': plug possible refleak (closes #13199) http://hg.python.org/cpython/rev/53c87a0275ab New changeset 7bf70519795c by Benjamin Peterson in branch 'default': merge 3.2 (#13199) http://hg.python.org/cpyt

[issue13199] slice_richcompare() might leak an object in rare cases

Changes by Meador Inge : -- nosy: +meador.inge stage: -> test needed type: -> resource usage versions: +Python 2.7, Python 3.2, Python 3.3 ___ Python tracker ___ __

[issue13199] slice_richcompare() might leak an object in rare cases

New submission from Sven Marnach : If exactly one of the two tuple allocations in [1] fails, the tuple that is successfully allocated won't be freed. (This probably never happened. Are you interested in this kind of bug report anyway?) [1]: http://hg.python.org/cpython/file/f6b3ad301851/Obje