Erik de Castro Lopo wrote:
Unfortunately, it seems that openssl allocates memory inside the
call to SSL_library_init() that seems to never get deallocated.
Would you people be interested in a patch that adds an
SSL_library_release() function that releases all memory and returns
the SSL library to the state it was in before SSL_library_init()
was called?
Is this still true after calling:
// Thread local cleanup
ERR_remove_state(0);
// Engine cleanup
ENGINE_cleanup();
CONF_modules_unload(1);
ERR_free_strings();
EVP_cleanup();
CRYPTO_cleanup_all_ex_data();
Maybe the problem is the confusing and non-obvious naming conventions.
* Developers should be forced to call initilization code before using
any part of the library (no implicit init).
* Any initilization code should have an accompanying cleanup function
following some arbitrary naming convention.
At the moment there is a patchwork of components each with differing
schemes (explicit or implicit initialization) and the cleanup functions
you need to use aren't an obvious naming choice in relation to the
init() function you called. So you have a right to be confused.
Darryl
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]
