[SciPy-user] How to free unused memory by Python

william ratcliff william.ratcliff at gmail.com
Mon Sep 3 09:35:31 EDT 2007


I never used it, but have you tried using valgrind?


Cheers,
William

On 9/3/07, massimo sandal <massimo.sandal at unibo.it> wrote:
>
> Anne Archibald ha scritto:
> > If it is memory exhaustion, all this business about "not freeing
> > memory back to the OS" is a red herring. No matter how old your
> > version of python and how little memory it ever releases back to the
> > OS, new objects will be allocated from the memory the python process
> > already has. If your process keeps growing indefinitely, that's not
> > malloc, that's your code keeping references to more and more data so
> > that it cannot be free()d. Perhaps look into tools for debugging
> > memory leaks in python?
>
> I'd love to find one. I have memory leaks here and there in my code (no
> doubt due to dangling references) but it is often damn hard to debug
> them. I asked on comp.lang.python but I found no useful answers. If you
> know of a memory debugging tool for python, let us know!
>
> m.
>
> --
> Massimo Sandal
> University of Bologna
> Department of Biochemistry "G.Moruzzi"
>
> snail mail:
> Via Irnerio 48, 40126 Bologna, Italy
>
> email:
> massimo.sandal at unibo.it
>
> tel: +39-051-2094388
> fax: +39-051-2094387
>
> _______________________________________________
> SciPy-user mailing list
> SciPy-user at scipy.org
> http://projects.scipy.org/mailman/listinfo/scipy-user
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.scipy.org/pipermail/scipy-user/attachments/20070903/734bf5c7/attachment.html>


More information about the SciPy-User mailing list