[New-bugs-announce] [issue13199] slice_richcompare() might leak an object in rare cases

[Sven Marnach]

New submission from Sven Marnach <sven at marnach.net>:

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/Objects/sliceobject.c#l349

----------
components: Interpreter Core
messages: 145689
nosy: smarnach
priority: normal
severity: normal
status: open
title: slice_richcompare() might leak an object in rare cases

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue13199>
_______________________________________