Re: Memory leak in SSL_CTX_new / SSL_CTX_free thru a call to CRYPTO_get_ex_new_index()

[Richard Levitte - VMS Whacker]

From: "Martin Skinner" <[EMAIL PROTECTED]>

N8Schwaermer> So, a single call to CRYPTO_get_ex_new_index() allocated
N8Schwaermer> these memory blocks and nothing frees them.
N8Schwaermer> Am I missing something?

This is perfectly normal.  What happens is that a number of functions
are registered for a "type" (completely defined by the caller) of extra
data.  This structure of pointers is then stored in a stack, and
that's what you see being allocated in your tracebacks .  Since it's
meant to be possible to reuse, given an index into that stack, it's
stored globally and stays around for the lifetime of the proocess.

There's a reason there's a call to MemCheck_off() in the beginning of
CRYPTO_get_ex_new_index()  :-)...

-- 
Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken   \ S-168 35  BROMMA  \ T: +46-8-26 52 47
Redakteur@Stacken   \      SWEDEN       \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis                -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/

Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]