Understanding memory leak reports

[Giampaolo Rodola']

On 22 Dic, 01:27, Ross Ridge <rri... at caffeine.csclub.uwaterloo.ca>
wrote:
> Giampaolo Rodola' <gne... at gmail.com> wrote:
> >I'm in a big trouble since I don't know how to find some memory leaks
> ...
> >The message printed on screen is the following:
>
> >gc: collectable <function 00C70E70>
> >gc: collectable <type 00B41018>
> >gc: collectable <dict 00C6DE40>
> >gc: collectable <tuple 00C09900>
> >gc: collectable <tuple 00BCD510>
> >gc: collectable <function 00C70EB0>
> >gc: collectable <function 00C70E30>
>
> >Since the main module is very big (more than 2800 lines of code) I do
> >not understand which objects are not garbage collected.
>
> They are being garbage collected.  That's what the "collectable" part
> of the message means.  It's just a warning that those objects needed
> to be garbage collected because they were refering to each other in
> some sort of cycle.  While the memory used was being wasted before the
> garbage collector ran, it probably doesn't have any negative effect on
> your program.
>
>                                                 Ross Ridge

Uhm... that's a good news altough it doesn't seem to me that I used
any sort of cicle.
Thank you.