On 8/30/07, 7stud <[EMAIL PROTECTED]> wrote:
> On Aug 30, 12:36 pm, "Chris Mellon" <[EMAIL PROTECTED]> wrote:
> > On 8/30/07, 7stud <[EMAIL PROTECTED]> wrote:
> >
> > > On Aug 30, 3:50 am, "Martin v. Löwis" <[EMAIL PROTECTED]> wro
On Aug 30, 12:36 pm, "Chris Mellon" <[EMAIL PROTECTED]> wrote:
> On 8/30/07, 7stud <[EMAIL PROTECTED]> wrote:
>
> > On Aug 30, 3:50 am, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > > > gc.set_debug(gc.DEBUG_LEAK)
> &
On 8/30/07, 7stud <[EMAIL PROTECTED]> wrote:
> On Aug 30, 3:50 am, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > > gc.set_debug(gc.DEBUG_LEAK)
> > > print gc.garbage
> >
> > > --output:--
> > > []
> > > gc: uncollectabl
On Aug 30, 3:50 am, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > gc.set_debug(gc.DEBUG_LEAK)
> > print gc.garbage
>
> > --output:--
> > []
> > gc: uncollectable
> > gc: uncollectable
> > gc: uncollectable
> > gc: unco
On Aug 30, 3:50 am, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > gc.set_debug(gc.DEBUG_LEAK)
> > print gc.garbage
>
> > --output:--
> > []
> > gc: uncollectable
> > gc: uncollectable
> > gc: uncollectable
> > gc: unco
> gc.set_debug(gc.DEBUG_LEAK)
> print gc.garbage
>
> --output:--
> []
> gc: uncollectable
> gc: uncollectable
> gc: uncollectable
> gc: uncollectable
gc.garbage is filled only after these messages
are printed, not before. You need to add an explicit
call to gc.c
gc.garbage returns an empty list even though the command:
gc.set_debug(gc.DEBUG_LEAK)
produces the following output:
gc: uncollectable
gc: uncollectable
gc: uncollectable
gc: uncollectable
I expected all those objects to be in the list returned by
gc.garbage. Here's the code:
impo
s,
since you could always arrange to release them eventually through
explicit Python code.
> I played with other flags as DEBUG_SAVEALL, but I think they are not
> useful for what I want.
DEBUG_LEAK includes DEBUG_SAVEALL; all objects in cycles are not
released, but added to gc.garbage. This is t
with __del__ methods that are
involved in cycles. Get rid of the __del__ methods or figure out some way
to break the cycles.
Cesar> Finally, in this group I have seen a reference to an article in
Cesar> which they had the look to gc.garbage after calling explicitally
Cesar> to
determine if
there is a leak in the python code? (the value rises). I am not
totally sure (see below).
I played with other flags as DEBUG_SAVEALL, but I think they are not
useful for what I want.
Finally, in this group I have seen a reference to an article in which
they had the look to gc.garbage
10 matches
Mail list logo