We are testing our application (that uses OpenSSL for FTPS) to check the
memory leak over time(continuous FTPS upload is performed for about 12
hours).
We observed that the memory consumed by the process is reduced(about 3MB)
after 6 mins.
Kindly let us know if it is related to the SSL session
Thank you fro your reply.
We have already called SSL_free() API.
We are using SSL APIs for FTPS file transfer.
Please find the below sample code .
//The below code is implemented for Control connection.
void LoadSSLModules(void)
{
SSL_load_error_strings();
ERR_load_ERR_strings();
We observed that sometimes SSL_Shudown() is not returning success.
If the cache is maintained, will the API fail.
--
View this message in context:
http://openssl.6102.n7.nabble.com/openssl-memory-leak-tp52311p52361.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
The openssl source package includes a generic server (s_server) and client
(s_client).
My first suspect when something has a memory leak with SSL connections only is
to check whether SSL contexts returned by SSL_new() always get cleaned up later
by calling SSL_free()...
Andrew
-Original
After some investigation I've figured out that the memory leak isn't caused
by running Openssl in threads. However, after about 200 connections, may
vary, the used memory increases with around 70 kb. Is this normal? I guessed
it's allocated by the openssl library
2009/5/6 Fabian Bergmark
, 2009 4:49 PM
Subject: Re: Openssl Memory leak
After some investigation I've figured out that the memory leak isn't caused
by running Openssl in threads. However, after about 200 connections, may vary,
the used memory increases with around 70 kb. Is this normal? I guessed it's
allocated
Okey. Now i got no more memory leaks when I put the SSL code in main.
However, if i try to put the exact same code in a thread the memory leak is
back.
Here is the essential code I'm using;
void lcserver::start()
{
SSL_library_init();
SSL_load_error_strings();
method = SSLv23_server_method();
Hi,
Check the return value of SSL_shutdown(ssl). Sometimes it needs up to 4
iterations to complete due to internal state machine. It completes when the
value != 0. Hope it helps.
BR,
Nikos
- Original Message -
From: Fabian Bergmark
To: openssl-users@openssl.org
Sent: