Message148750
| Author |
vstinner |
| Recipients |
Trundle, ncoghlan, neologix, pitrou, tim.peters, vstinner |
| Date |
2011年12月02日.01:11:56 |
| SpamBayes Score |
1.1738376e-06 |
| Marked as misclassified |
No |
| Message-id |
<1322788318.0.0.665322459556.issue13390@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
The overhead on PyObject_Malloc() is just an increment on an integer, so it is very low (or null).
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?
> I think we should hide at least the initial implementation
> behind PY_REF_DEBUG until we're sure we've worked the kinks
> out of it.
Programs not always behave exactly the same in debug or in release mode. Sometimes, bugs disappear in debug mode :-(
If the feature is written to track memory leaks in the CPython test suite, it's ok to only expose the function in debug mode.
> Right now this patch will allow to enrich the daily refleak runs
Did you already found real leaks using your hack^Wpatch? (was c6dafa2e2594 found by your tool?) |
|