Message148769
| Author |
pitrou |
| Recipients |
Trundle, dmalcolm, ncoghlan, neologix, pitrou, tim.peters, vstinner |
| Date |
2011年12月02日.18:12:05 |
| SpamBayes Score |
0.00027848902 |
| Marked as misclassified |
No |
| Message-id |
<1322849526.99.0.620381425983.issue13390@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> 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 :-)). |
|