On Dec 21, 1:44 pm, "Giampaolo Rodola'" <[EMAIL PROTECTED]> wrote:
> Since the main module is very big (more than 2800 lines of code)
maybe that is the actual problem to begin with,
you should refactor it so it it more modular and trackable, otherwise
this is just one of the many issues that wil
On 22 Dic, 01:27, Ross Ridge <[EMAIL PROTECTED]>
wrote:
> Giampaolo Rodola' <[EMAIL PROTECTED]> 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
> >gc: collectable
> >gc: collectable
> >g
Giampaolo Rodola' <[EMAIL PROTECTED]> 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
>gc: collectable
>gc: collectable
>gc: collectable
>gc: collectable
>gc: collectable
>gc: collectable
>
On 21 Dic, 20:10, [EMAIL PROTECTED] wrote:
> On Dec 21, 12:44 pm, "Giampaolo Rodola'" <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > Hi,
> > I'm in a big trouble since I don't know how to find some memory leaks
> > I just discovered in a program of mine.
> > By putting:
>
> > import gc
> > gc.set_debug(g
On Dec 21, 12:44 pm, "Giampaolo Rodola'" <[EMAIL PROTECTED]> wrote:
> Hi,
> I'm in a big trouble since I don't know how to find some memory leaks
> I just discovered in a program of mine.
> By putting:
>
> import gc
> gc.set_debug(gc.DEBUG_LEAK)
>
> ..at the end of a script which imports a module I
Hi,
I'm in a big trouble since I don't know how to find some memory leaks
I just discovered in a program of mine.
By putting:
import gc
gc.set_debug(gc.DEBUG_LEAK)
..at the end of a script which imports a module I wrote it seems I
have some memory leaks scattered around.
The message printed on sc
