There is one small memory leak that can't be removed without changing the library, but the author's are aware of it. It is caused when the function CRYPTO_get_ex_new_index() is called. It gets called when SSL_CTX_new() is called. See the thread http://www.mail-archive.com/openssl-users@openssl.org/msg11445.html). _____________________________________ Greg Stark Ethentica, Inc. [EMAIL PROTECTED] _____________________________________ ----- Original Message ----- From: "Harald Koch" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, April 19, 2001 4:48 PM Subject: Re: Memory Leaks.. > > CRYPTO_malloc() in .\crypto\mem.c > > ERR_get_state() in .\crypto\err.c > > ERR_clear_error() in .\crypto\err.c > > ASN1_d2i_bio() in .\crypto\asn1\a_d2i_fp.c > > d2iX509_CRL_bio() in .\crypto\x509\x_all.c > > main() > > mainCRTStartup() > > > > void > openssl_cleanup(void) > { > // Clean up OpenSSL globals > SSL_CTX_flush_sessions(ACE_SSL_Context::instance()->context(), 0); > ERR_remove_state(0); > ERR_free_strings(); > EVP_cleanup(); > } > > > There may be others; that's all we've needed so far to get rid of our > memory leak warnings. The "ERR_remove_state(0)" call is the one that > will do it for you... > > -- > Harald Koch <[EMAIL PROTECTED]> > > "It takes a child to raze a village." > -Michael T. Fry > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development 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]
