New submission from Stefan Krah <stefan-use...@bytereef.org>: This is one of two remaining "definitely lost" leaks in py3k. It started to appear in r70459. How to reproduce:
make distclean && ./configure OPT="-O0 -g" --without-pymalloc && make valgrind --leak-check=full --suppressions=Misc/valgrind-python.supp ./python > VGOUT 2>&1 Then search for 'definitely'. This leak is not present in release-2.7. ==2058== 56 bytes in 1 blocks are definitely lost in loss record 918 of 2,136 ==2058== at 0x4C2412C: malloc (vg_replace_malloc.c:195) ==2058== by 0x4167DE: _PyObject_New (object.c:243) ==2058== by 0x42C278: _PyUnicode_New (unicodeobject.c:341) ==2058== by 0x4306BD: PyUnicodeUCS2_DecodeUTF8Stateful (unicodeobject.c:2100) ==2058== by 0x430671: PyUnicodeUCS2_DecodeUTF8 (unicodeobject.c:2065) ==2058== by 0x42C8F7: PyUnicodeUCS2_FromStringAndSize (unicodeobject.c:541) ==2058== by 0x42C973: PyUnicodeUCS2_FromString (unicodeobject.c:559) ==2058== by 0x50B432: PyDict_SetItemString (dictobject.c:2088) ==2058== by 0x4258DF: PyType_Ready (typeobject.c:3844) ==2058== by 0x517B64: PyStructSequence_InitType (structseq.c:522) ==2058== by 0x4F3B4F: _PyFloat_Init (floatobject.c:1905) ==2058== by 0x4813CE: Py_InitializeEx (pythonrun.c:217) ---------- components: Interpreter Core messages: 119226 nosy: mark.dickinson, skrah priority: normal severity: normal status: open title: Memory leak (r70459) type: behavior versions: Python 3.2 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue10156> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
