[issue13020] structseq.c: refleak

2012-02-14 Thread Antoine Pitrou
Antoine Pitrou added the comment: I've now committed the patch. Thanks for contributing! -- nosy: +pitrou resolution: -> fixed stage: test needed -> committed/rejected status: open -> closed versions: +Python 2.7, Python 3.2, Python 3.3 ___ Python t

[issue13020] structseq.c: refleak

2012-02-14 Thread Roundup Robot
Roundup Robot added the comment: New changeset 6454e5de7c34 by Antoine Pitrou in branch '3.2': Issue #13020: Fix a reference leak when allocating a structsequence object fails. http://hg.python.org/cpython/rev/6454e5de7c34 New changeset 5e0085d67f65 by Antoine Pitrou in branch 'default': Issue

[issue13020] structseq.c: refleak

2012-01-19 Thread Torsten Landschoff
Torsten Landschoff added the comment: +1 for the patch. All the error paths above the change do Py_DECREF(arg); return NULL; arg is initialized with PySequence_Fast, which returns a new reference. Hard to create a test case for this... -- nosy: +torsten __

[issue13020] structseq.c: refleak

2011-09-21 Thread Meador Inge
Meador Inge added the comment: In general I agree that a test case is needed, but in this particular case its looks to be non-trivial to come up with one. The only way the reference leak is triggered is when memory is exhausted during an attempt to new up a 'PyStructSequence' object. -

[issue13020] structseq.c: refleak

2011-09-21 Thread Stefan Krah
Changes by Stefan Krah : -- title: Resource is not released before returning from the functiion -> structseq.c: refleak ___ Python tracker ___ __