[xmlsec] FW: Free/Destroy versus Memory Leak

Ed Shallow ed.shallow at rogers.com
Mon Feb 20 07:49:48 PST 2006

Some news,

   With all due respect, I know how Python does memory management. I
verified all the automatic garbage collection in my app before I
decided to post this message. I also traced all garbage collection
using the gc Python module and coded __del__ methods everywhere. Enough
history ...

  Here are sum more insights after further testing and process of

- no leaks whatsoever on Fedora4 with 1.2.9 OpenSSL and pyxmlsec

- no leaks whatsoever on Fedora4 with 1.2.9 OpenSSL and Python ctypes

- Now here is the surprise ... no leaks whatsoever on Windows with
Igor's 1.2.8 binaries using OpenSSL and Python ctypes

   As soon as I flip to mscrypto (a 1 line change), I get 30K - 40K
memory expansion per request.

   This seems to strongly implicated xmlsec-mscrypto. Do you not agree



--- Aleksey Sanin <aleksey at aleksey.com> wrote:
> BTW, are you using Python? If "yes" then you might want to check
> how does python do memory management on Windows. It might not be
> a real leak but "normal" behavior.
> Aleksey

More information about the xmlsec mailing list