[pypy-issue] [issue707] PyPy memory leak in 1.5 on OSX

Justin Peel tracker at bugs.pypy.org
Sat Sep 17 17:52:33 CEST 2011

Justin Peel <peelpy at gmail.com> added the comment:

Pyexpat wasn't allowing the parser object to be collected because it put each 
parser in a global_storage container. I used a weakref and memory seems to be 
under control. The pyexpat_leak.py code I put up maxes out just over 100 MB no 
matter how many loops are done. Albert's code now maxes out at about 25MB for me 
rather than over 600 MB.

status: chatting -> resolved

PyPy bug tracker <tracker at bugs.pypy.org>

More information about the pypy-issue mailing list