This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: slice_richcompare() might leak an object in rare cases
Type: resource usage Stage: resolved
Components: Interpreter Core Versions: Python 3.2, Python 3.3, Python 2.7
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: Nosy List: meador.inge, python-dev, smarnach
Priority: normal Keywords:

Created on 2011-10-17 13:23 by smarnach, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (2)
msg145689 - (view) Author: Sven Marnach (smarnach) Date: 2011-10-17 13:23
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
msg145730 - (view) Author: Roundup Robot (python-dev) (Python triager) Date: 2011-10-17 17:10
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/cpython/rev/7bf70519795c
History
Date User Action Args
2022-04-11 14:57:22adminsetgithub: 57408
2011-10-17 17:10:37python-devsetstatus: open -> closed

nosy: + python-dev
messages: + msg145730

resolution: fixed
stage: test needed -> resolved
2011-10-17 13:30:14meador.ingesetnosy: + meador.inge
stage: test needed
type: resource usage

versions: + Python 2.7, Python 3.2, Python 3.3
2011-10-17 13:23:44smarnachcreate