[xmlsec] FW: Free/Destroy versus Memory Leak
ed.shallow at rogers.com
Mon May 1 19:03:41 PDT 2006
It is not just the verify that leaks. The sign leaks as well. Here is a
very simple signing template. <KeyName> triggers which key to access in
mscrypto store. Everything works fine, it just leaks.
xmlsec sign --crypto mscrypto --repeat 1000 --output
From: Edward Shallow [mailto:ed.shallow at rogers.com]
Sent: May 1, 2006 9:57 PM
To: 'Aleksey Sanin'
Cc: 'xmlsec at aleksey.com'; 'Dmitry Belyavsky'
Subject: RE: [xmlsec] FW: Free/Destroy versus Memory Leak
I tried a few more combinations. It seems to be related to the <KeyName>
element which was used at signing to tell mscrypto what key to use. It is
left over from that original sign activity.
If you take <KeyName> out altogether it still works (probably uses key
directly from X509Certificate) and leaks much less, but it still leaks a
If it is left in and the <KeyName> exists in crypto store, it goes and gets
it but seems not to free it and it leaks fast.
If it is left in and the <KeyName> does not exist in crypto store, it still
works, and it only leaks a bit.
Hope this helps.
From: Aleksey Sanin [mailto:aleksey at aleksey.com]
Sent: May 1, 2006 9:17 PM
To: ed.shallow at rogers.com
Cc: xmlsec at aleksey.com; 'Dmitry Belyavsky'
Subject: Re: [xmlsec] FW: Free/Destroy versus Memory Leak
> xmlsec verify --crypto mscrypto --repeat 1000 --trusted-der
> keys/upu-cacert.der inout/edsigned-enveloped.xml
> The run started off at around 4800K and ended up around 45,000K I
> changed --repeat to 2000 and I ended up at 86,000K
OK, I don't see any leaks on my test... Can you send the files you use in
this run, please?
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1015 bytes
Desc: not available
Url : http://www.aleksey.com/pipermail/xmlsec/attachments/20060501/47cfe066/tmpl-EPM-sign-enveloped-friendly-0002.xml
More information about the xmlsec