>>OpenSSL artifacts that are created by the application, then handed to
>>some other part of the API for use, so who is now responsible for the
>>destructions of them? That kind of misunderstanding.
>>Darryl
Hi Darryl,
To an extent you are correct. We have fixed the issue and it is due to our
usage and clean up of openSSL BIOs. We have a BIO pair we got misled by the
reference in following book that SSL_free will clean all the associated
BIOs.
Book "Network Security with OpenSSL By Pravir Chandra, Matt Messier,
John
Viega", Page:137, following paragraph.
"The last point to make about this example is that we removed the call
to
BIO_free.
This is done because SSL_free automatically frees the SSL object's
underlying BIOs for us."
But later while we were referring to the documentation on openssl website,
we came to know that SSL_free cleans up only one haf of the BIO pair where
as the other half need to be cleaned using BIO_free. After adding this piece
of code, the memory leak has vanished.
Thanks for your guidance.
Regards
Vijay
--
View this message in context:
http://old.nabble.com/Memory-leak-issue-in-openssl-tp26297284p26542913.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
