[issue31408] Leak in typeobject.c

2017-09-12 Thread Stefan Krah
Stefan Krah added the comment: It's fixed, thanks! -- resolution: -> duplicate stage: needs patch -> resolved status: open -> closed superseder: -> Reference leaks introduced by bpo-30860 ___ Python tracker

[issue31408] Leak in typeobject.c

2017-09-11 Thread Eric Snow
Eric Snow added the comment: @skrah, could you see if the PR for issue #31420 resolves this? I'm guessing it won't, but you indicated that the two issues might be related. Thanks! -- ___ Python tracker

[issue31408] Leak in typeobject.c

2017-09-10 Thread INADA Naoki
INADA Naoki added the comment: Maybe, PyDict_ClearFreeList() is not called? -- nosy: +inada.naoki ___ Python tracker ___ ___ Python-b

[issue31408] Leak in typeobject.c

2017-09-10 Thread Stefan Krah
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==