This was a known bug in 0.9.6b; I don't know if it is fixed in the current snapshot. Since the amount of memory leaked is small and fixed, correcting the bug was deemed to be low priority. As far as I know, there is no way to free up the memory other than adding your own code to the openssl package.
====================== Greg Stark [EMAIL PROTECTED] ====================== ----- Original Message ----- From: "Ramaprasad K.R" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 04, 2001 10:30 AM Subject: [Fwd: memory allocated by SSL_CTX_new] > Hi, > > Looks like the earlier message that I sent did not reach the list. So I am > resending again. Could somebody help with this please. > > Regards > Rampi > > -------- Original Message -------- > Subject: memory allocated by SSL_CTX_new > Date: Thu, 27 Sep 2001 19:49:27 +0530 > From: "Ramaprasad K.R" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > > Hello, > > When I call SSL_CTX_new, the function CRYPTO_get_ex_new_index() gets called > and it seems to be allocating 56 bytes. And this memory does not get freed > when I do a SSL_CTX_free() ? > > Could you please let me know if I need to call some other routine to > ensure that those 56 bytes are also freed up. > > Thanks in advance, > Rampi > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List [EMAIL PROTECTED] > Automated List Manager [EMAIL PROTECTED] > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
