Great news! I am glad to hear that the memory leak
problem is solved!
Can you get stack trace for the crash, please? I am
sure it is something trivial like libraries mismatch :)
Aleksey
___
xmlsec mailing list
xmlsec@aleksey.com
http://www.aleksey.co
E: [xmlsec] FW: Free/Destroy versus Memory Leak
Forgot to mention. It only crashes with mscrypto.
-Original Message-
From: Edward Shallow [mailto:[EMAIL PROTECTED]
Sent: May 6, 2006 5:53 PM
To: '[EMAIL PROTECTED]'; 'Aleksey Sanin'
Cc: 'xmlsec@aleksey.com'
Subj
Forgot to mention. It only crashes with mscrypto.
-Original Message-
From: Edward Shallow [mailto:[EMAIL PROTECTED]
Sent: May 6, 2006 5:53 PM
To: '[EMAIL PROTECTED]'; 'Aleksey Sanin'
Cc: 'xmlsec@aleksey.com'
Subject: RE: [xmlsec] FW: Free/Destroy
ginal Message-
From: Edward Shallow [mailto:[EMAIL PROTECTED]
Sent: May 6, 2006 4:41 PM
To: 'Aleksey Sanin'
Cc: 'xmlsec@aleksey.com'
Subject: RE: [xmlsec] FW: Free/Destroy versus Memory Leak
OK link.exe /lib works ... finally got it all compiled and linked. Ran into
more &quo
is still there ...
Stay tuned ...
Thanks again Aleksey,
Ed
-Original Message-
From: Aleksey Sanin [mailto:[EMAIL PROTECTED]
Sent: May 6, 2006 1:17 PM
To: [EMAIL PROTECTED]
Cc: xmlsec@aleksey.com
Subject: Re: [xmlsec] FW: Free/Destroy versus Memory Leak
This is what go
;
Stop.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Aleksey Sanin
Sent: May 5, 2006 5:44 PM
To: [EMAIL PROTECTED]
Cc: xmlsec@aleksey.com
Subject: Re: [xmlsec] FW: Free/Destroy versus Memory Leak
- Got passed the missing "C" runtime stuff, now
: 'lib.exe' : return code '0x1'
Stop.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Aleksey Sanin
Sent: May 5, 2006 5:44 PM
To: [EMAIL PROTECTED]
Cc: xmlsec@aleksey.com
Subject: Re: [xmlsec] FW: Free/Destroy versus Memory Leak
- Got passed the missing "C" runtime stuff, now I am failing on
openssl-related include's
You need to set correct OpenSSL version in the mycfg.bat file. E.g.
if you use OpenSSL 0.9.8 then you should have something like this:
--crypto=mscrypto,openssl=098
P.S. Are the warnings on xmlse
509StoreCtx'
..\src\openssl\x509vfy.c(591) : error C2037: left of 'xst' specifies
undefined struct/union '_xmlSecOpenSSLX509StoreCtx'
..\src\openssl\x509vfy.c(591) : error C2037: left of 'vpm' specifies
undefined struct/union '_xmlSecOpenSSLX509StoreCtx'
.
Edward Shallow wrote:
Almost there. Can't find msvcrt.lib
Not in MSSDK or VC6 ???
Ed
This is MS runtime library... Yet another MS download:
http://wiki.tcl.tk/11431
Aleksey
___
xmlsec mailing list
xmlsec@aleksey.com
http://www.aleksey.com/mailm
ECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Edward Shallow
Sent: May 2, 2006 11:06 PM
To: 'Aleksey Sanin'
Cc: xmlsec@aleksey.com; [EMAIL PROTECTED]
Subject: RE: [xmlsec] FW: Free/Destroy versus Memory Leak
PostScript:
I am downloading the Platform SDK. That should do it. I'll k
ED]
Subject: RE: [xmlsec] FW: Free/Destroy versus Memory Leak
The link to the Visual Studio C++ 2003 Toolkit (free) provided to me by
Dmitry (thanks) contains ***NO*** nmake.exe
I had a tough time finding this old one. Any suggestions ?
Ed
-Original Message-
From: Aleksey Sanin [mailto:[
I had a tough time finding this old one. Any suggestions ?
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/
Aleksey
___
xmlsec mailing list
xmlsec@aleksey.com
http://www.aleksey.com/mailman/listinfo/xmlsec
PROTECTED]
Cc: xmlsec@aleksey.com; [EMAIL PROTECTED]
Subject: Re: [xmlsec] FW: Free/Destroy versus Memory Leak
> C:\XMLSec\xmlsec1-1.2.9\win32>nmake
>
> Microsoft (R) Program Maintenance Utility Version 1.50
> Copyright (c) Microsoft Corp 1988-94. All rights reserved.
>
> makefi
C:\XMLSec\xmlsec1-1.2.9\win32>nmake
Microsoft (R) Program Maintenance Utility Version 1.50
Copyright (c) Microsoft Corp 1988-94. All rights reserved.
makefile(571) : fatal error U1088: invalid separator '::' on inference rule
Stop.
The nmake you run is *very* old (version 1.50 from 1994). It
: fatal error U1088: invalid separator '::' on inference rule
Stop.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Aleksey Sanin
Sent: May 2, 2006 10:44 AM
To: [EMAIL PROTECTED]
Cc: xmlsec@aleksey.com; [EMAIL PROTECTED]
Subject: Re: [xmlsec] FW: F
You do not see it with the sign ?
I do see memory growth with both sign and verify... but I don't see
anything in Purify.
Do you think it could be the environment around xmlsec ?
I highly doubt that.
Might this not leak on a freshly installed XP machine ?
Same. It *might* depend on Servi
Message-
From: Aleksey Sanin [mailto:[EMAIL PROTECTED]
Sent: May 2, 2006 12:17 AM
To: [EMAIL PROTECTED]
Cc: xmlsec@aleksey.com
Subject: Re: [xmlsec] FW: Free/Destroy versus Memory Leak
OK, I believe that the attached patch fixes the memory leak though I don't
see it in Purify. Please, l
OK, I believe that the attached patch fixes the memory leak though
I don't see it in Purify. Please, let me know if it works for you
or not.
Thank you in advance!
Aleksey
Index: src/mscrypto/x509.c
===
RCS file: /cvs/gnome/xmlsec/sr
-friendly.xml
tmpl/tmpl-EPM-sign-enveloped-friendly.xml
Ed
-Original Message-
From: Edward Shallow [mailto:[EMAIL PROTECTED]
Sent: May 1, 2006 9:57 PM
To: 'Aleksey Sanin'
Cc: 'xmlsec@aleksey.com'; 'Dmitry Belyavsky'
Subject: RE: [xmlsec] FW: Free/Destroy versus Memor
Here they are ...
Thanks
-Original Message-
From: Aleksey Sanin [mailto:[EMAIL PROTECTED]
Sent: May 1, 2006 9:17 PM
To: [EMAIL PROTECTED]
Cc: xmlsec@aleksey.com; 'Dmitry Belyavsky'
Subject: Re: [xmlsec] FW: Free/Destroy versus Memory Leak
> xmlsec verify --crypto mscr
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
Subject: FW: [xmlsec] FW: Free/Destroy versus Memory Leak
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 me
xmlsec.dll
xmlsec.exe
It would be enormously appreciated.
Cheers,
Ed
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Aleksey Sanin
Sent: February 20, 2006 5:43 PM
To: [EMAIL PROTECTED]
Cc: xmlsec@aleksey.com
Subject: Re: [xmlsec] FW: Free/Destroy versus M
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
Index: src/mscrypto/certkeys.c
===
RCS
That is good. Please see my other post with --repeat results.
If it is environmental or version-specific that is great news. It means
it can be fixed.
As I said, I am using Igor's 1.2.8 binaries.
I will try GlowCode 5.1 next, but it does not seem to be Python or
ctypes (crossing my fingers ;)
E
mber of
> repetitions.
> Task manager should be enough to spot it if there is a 40kb leak per
> operation...
>
> Bye.
> Amiler
>
>
> >From: Aleksey Sanin <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >CC: xmlsec@aleksey.com
> >Subject: Re: [
I run xmlsec utility for signature/verification/encryption/decryption
with RSA keys and certificates under purify and I see no leaks. Can
you describe what exactly are you doing, please?
Aleksey
___
xmlsec mailing list
xmlsec@aleksey.com
http://www.alek
of
> repetitions.
> Task manager should be enough to spot it if there is a 40kb leak per
> operation...
>
> Bye.
> Amiler
>
>
> >From: Aleksey Sanin <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >CC: xmlsec@aleksey.com
> >Subject: Re: [xmls
TED]>
To: [EMAIL PROTECTED]
CC: xmlsec@aleksey.com
Subject: Re: [xmlsec] FW: Free/Destroy versus Memory Leak
Date: Mon, 20 Feb 2006 10:50:23 -0800
Ed Shallow wrote:
Yes I hear you. It would be irrefutable if we could reproduce it with a
native "C" setup.
However, we need one tha
Ed Shallow wrote:
Yes I hear you. It would be irrefutable if we could reproduce it with a
native "C" setup.
However, we need one that makes multiple calls (signs, verifies,
encrypts, decrypts) per process before exiting. The command line starts
a new process for each operation and one cannot
Yes I hear you. It would be irrefutable if we could reproduce it with a
native "C" setup.
However, we need one that makes multiple calls (signs, verifies,
encrypts, decrypts) per process before exiting. The command line starts
a new process for each operation and one cannot measure the memory
pro
This seems to strongly implicated xmlsec-mscrypto. Do you not agree
?
Yes, this is a very good indication. Can you describe what are
you doing? If you can reproduce it with a command line for xmlsec
command line tool then it is even better!
Aleksey
_
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 ...
- xmlsec.xmlSecInit()
- xmlsec.xmlSecCryptoDLInit()
- xmlsec.xmlSecCryptoDLLoadLibrary('mscrypto')
- xmlsec.xmlSecCryptoAppInit('MY')
- xmlsec.xmlSecCryptoInit()
Everything else is on a request-by-request basis including:
- libxml2 parsed docs
- keysMngr
- keyStore
- dsig context
- enc context
Do you have any ideas or suggestions ?
Libxml2 memory debugger, Purify, Glowcode, valgrind, ...
Aleksey
___
xmlsec mailing list
xmlsec@aleksey.com
http://www.aleksey.com/mailman/listinfo/xmlsec
so need Entrust support and Entrust also has
an MS CAPI CSP.
I do not know if the Linux version of the app leaks.
-Original Message-
From: Daniel Veillard [mailto:[EMAIL PROTECTED]
Sent: February 19, 2006 5:56 PM
To: Edward Shallow
Cc: xmlsec@aleksey.com
Subject: Re: [xmlsec] FW: Free
On Sun, Feb 19, 2006 at 05:35:51PM -0500, Edward Shallow wrote:
> .. Re-sending ... 1st one bounced ..
>I have isolated the memory growth to the xmlsec environment by using
> successively narrower 'quick returns'.
> When I comment out the single xmlsec.xmlSecDSigCtxVerify(dsigCtx, sigNode)
> c
.. Re-sending ... 1st one bounced ..
-Original Message-
From: Edward Shallow [mailto:[EMAIL PROTECTED]
Sent: February 19, 2006 5:21 PM
To: 'xmlsec@aleksey.com'
Subject: Free/Destroy versus Memory Leak
Hi Aleksey,
I seem to have all the functionality challenges behind me in this late
39 matches
Mail list logo
