This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients Trundle, dmalcolm, ncoghlan, neologix, pitrou, tim.peters, vstinner
Date 2011-12-02.18:12:05
SpamBayes Score 0.000278489
Marked as misclassified No
Message-id <>
> The feature is interesting, but I'm not convinced that a very simple
> counter is enough to track memory leaks. It may help the CPython test
> suite, but what about real world application?

Good question. A simple counter is the only thing we can enable by default, though. Anything else would require recompiling Python, which is probably a barrier for most users.

> Did you already found real leaks using your hack^Wpatch? (was
> c6dafa2e2594 found by your tool?)

yes, c6dafa2e2594 was found with this patch. It's the only one, though (there's also a leak in test_ctypes but I don't want to investigate :-)).
Date User Action Args
2011-12-02 18:12:07pitrousetrecipients: + pitrou, tim.peters, ncoghlan, vstinner, Trundle, dmalcolm, neologix
2011-12-02 18:12:06pitrousetmessageid: <>
2011-12-02 18:12:06pitroulinkissue13390 messages
2011-12-02 18:12:05pitroucreate