[New-bugs-announce] [issue13089] parsetok.c: memory leak

Stefan Krah report at bugs.python.org
Sun Oct 2 10:50:16 CEST 2011


New submission from Stefan Krah <stefan-usenet at bytereef.org>:

Seen in test_mailbox:

==31621== 6 bytes in 2 blocks are definitely lost in loss record 27 of 10,370
==31621==    at 0x4C2154B: malloc (vg_replace_malloc.c:236)
==31621==    by 0x5271A5: parsetok (parsetok.c:179)
==31621==    by 0x526E8A: PyParser_ParseStringFlagsFilenameEx (parsetok.c:67)
==31621==    by 0x4BC385: PyParser_ASTFromString (pythonrun.c:1898)
==31621==    by 0x4BC1E1: Py_CompileStringExFlags (pythonrun.c:1842)
==31621==    by 0x478AB8: builtin_compile (bltinmodule.c:626)
==31621==    by 0x5759F3: PyCFunction_Call (methodobject.c:84)
==31621==    by 0x48F2CF: ext_do_call (ceval.c:4292)
==31621==    by 0x489992: PyEval_EvalFrameEx (ceval.c:2646)
==31621==    by 0x48E67B: fast_function (ceval.c:4068)
==31621==    by 0x48E3C7: call_function (ceval.c:4001)
==31621==    by 0x4895E1: PyEval_EvalFrameEx (ceval.c:2605)

----------
components: Interpreter Core
messages: 144763
nosy: skrah
priority: normal
severity: normal
stage: needs patch
status: open
title: parsetok.c: memory leak
type: resource usage
versions: Python 3.3

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


More information about the New-bugs-announce mailing list