New submission from Stefan Krah: I traced this valgrind result down to 2ebc5ce42a8a9e047e790aefbf9a94811569b2b6 :
==23495== 240 (72 direct, 168 indirect) bytes in 1 blocks are definitely lost in loss record 2,255 of 2,922 ==23495== at 0x4C2A9A1: malloc (vg_replace_malloc.c:299) ==23495== by 0x42C6BC: PyMem_RawMalloc (obmalloc.c:420) ==23495== by 0x42C6BC: _PyObject_Alloc (obmalloc.c:975) ==23495== by 0x42C6BC: _PyObject_Malloc (obmalloc.c:985) ==23495== by 0x448B78: _PyObject_GC_Alloc (gcmodule.c:1629) ==23495== by 0x448B78: _PyObject_GC_Malloc (gcmodule.c:1651) ==23495== by 0x448B78: _PyObject_GC_New (gcmodule.c:1663) ==23495== by 0x4A85B6: new_dict (dictobject.c:584) ==23495== by 0x4A85B6: PyDict_New (dictobject.c:624) ==23495== by 0x4AC8F0: PyDict_Copy (dictobject.c:2510) ==23495== by 0x4D68A7: set_names (typeobject.c:7138) ==23495== by 0x4D68A7: type_new (typeobject.c:2756) ==23495== by 0x4CAEC4: type_call (typeobject.c:922) ==23495== by 0x47344B: _PyObject_FastCallDict (call.c:125) ==23495== by 0x5497D2: builtin___build_class__ (bltinmodule.c:165) ==23495== by 0x4725AF: _PyMethodDef_RawFastCallKeywords (call.c:653) ==23495== by 0x4725AF: _PyCFunction_FastCallKeywords (call.c:726) ==23495== by 0x4283E0: call_function (ceval.c:4701) ==23495== by 0x4283E0: _PyEval_EvalFrameDefault (ceval.c:3218) ==23495== by 0x54D3C6: PyEval_EvalFrameEx (ceval.c:549) ==23495== by 0x54D3C6: _PyEval_EvalCodeWithName (ceval.c:4049) ---------- components: Interpreter Core messages: 301812 nosy: eric.snow, skrah priority: normal severity: normal stage: needs patch status: open title: Leak in typeobject.c type: resource usage versions: Python 3.7 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue31408> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
