Hi Aleksey,
I noticed that Igor has recompiled libxmlsec (now at 1.2.9), as well as
libxml2, and libxslt. They are now available at his site. We were anxiously
awaiting these upgrades.
Unfortunately he did not pick up your fix to the memory leak problem in
mscrypto that you fixed in February (attached and below) ? And I have no
idea which branch/trunk he may have used.
As you probably know our project has totally wrapped xmlsec and libxml2 in
Python using ctypes and absolutely everything is working fine with many
thanks to your excellent support. As such we have no MS VC6 software or
anything else MS and simply use Igor's pre-compiled binaries for our Windows
support. We have been running with the memory leak for awhile and things are
getting worse.
Can I trouble you to send me your versions of these Windows dll's:
libxmlsec-mscrypto.dll
libxmlsec-openssl.dll
libxmlsec.dll
xmlsec.exe
It would be enormously appreciated.
Cheers,
Ed
-----Original Message-----
From: xmlsec-bounces@xxxxxxxxxxx [mailto:xmlsec-bounces@xxxxxxxxxxx] On
Behalf Of Aleksey Sanin
Sent: February 20, 2006 5:43 PM
To: ed.shallow@xxxxxxxxxx
Cc: xmlsec@xxxxxxxxxxx
Subject: Re: [xmlsec] FW: Free/Destroy versus Memory Leak
OK, I was able to reproduce the leak on Windows XP (before I tried Win2K).
The attached patch fixes the leak by reordering MSCrypto key cleanup calls.
Thanks for reporting the problem!
Aleksey
xmlsec-mscrypto-memleak.diff
Description: Text document
ATT00028.txt
Description: Text document
_______________________________________________
xmlsec mailing list
xmlsec@xxxxxxxxxxx
http://www.aleksey.com/mailman/listinfo/xmlsec
| 
