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 neologix
Recipients Trundle, ncoghlan, neologix, pitrou, tim.peters
Date 2011-11-15.08:11:38
SpamBayes Score 5.48835e-06
Marked as misclassified No
Message-id <>
> Together with -R, it can help chase those memory leaks which aren't 
> reference leaks (see c6dafa2e2594).

Valgrind does a much better job at this: it will also show you where the leaked blocks were allocated.
OTOH, Valgrind is Linux-only and slow, but since I haven't used the '-R' option much, I don't know how usable this will be in practice (detecting memory leaks is one thing, identifying them is even better :-).
Date User Action Args
2011-11-15 08:11:39neologixsetrecipients: + neologix, tim.peters, ncoghlan, pitrou, Trundle
2011-11-15 08:11:39neologixsetmessageid: <>
2011-11-15 08:11:38neologixlinkissue13390 messages
2011-11-15 08:11:38neologixcreate