> This leak is caused by add_docstring, but it's supposed to leak. I wonder if
> there's a way to register some kind of on-exit handler in Python so that
> this can also be cleaned up?
import atexit
atexit.register(your_cleanup_function)
whose api is no args on input:
def your_cleanup_function()
Hello all
>
> I decided to upgrade to 1.0b2 just to see what I get and now I get 7kB of
> "possibly lost" memory, coming from PyObject_Malloc (in
> /usr/lib/libpython2.4.so.1.0). This is a constant 7kB, however, and it
> isn't getting any larger if I increase the loop iterations. Looks good
> the
On 8/17/06, Robert Kern <[EMAIL PROTECTED]> wrote:
David Grant wrote:> Hello all,>> I had a massive memory leak in some of my code. It would basically end> up using up all 1GB of my RAM or more if I don't kill the application. I> managed to finally figure out which portion of the code was causing t
David Grant wrote:
> Hello all,
>
> I had a massive memory leak in some of my code. It would basically end
> up using up all 1GB of my RAM or more if I don't kill the application. I
> managed to finally figure out which portion of the code was causing the
> leak (with great difficulty) and have
Hello all,I had a massive memory leak in some of my code. It would basically end up using up all 1GB of my RAM or more if I don't kill the application. I managed to finally figure out which portion of the code was causing the leak (with great difficulty) and have a little example which exposes the
