[EMAIL PROTECTED] wrote: > > I was wondering if this is a known issue with this particular release of > OPEN SSL Crypto library. The dll I ran BoundsChecker against is > Lib32eay.dll, and > the reported memory leak indicates 16 bytes of allocated memory through > Crypto_malloc function in \crypto\mem.c. This function gets called ~2500 > in a > single client/server mutual authentication session using X.509 certs, with > a total memory leak of ~50k. >
There are no known cumulative memory leaks in OpenSSL: that is leaks that can increase in size. A few fixed length leaks can occur when some static tables are allocated but most of those have been eliminated in newer versions of OpenSSL. The functions Crypto_malloc() is what OpenSSL uses for memory allocation. So saying there's a leak in something which calls Crypto_malloc() is equivalent to saying that theres a leak in something which calls malloc(): i.e. not very helpful :-) Steve. -- Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/ Personal Email: [EMAIL PROTECTED] Senior crypto engineer, Gemplus: http://www.gemplus.com/ Core developer of the OpenSSL project: http://www.openssl.org/ Business Email: [EMAIL PROTECTED] PGP key: via homepage. ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
