Hi DS How do we handle closure in openssl??? . I just call: SSL_shutdown(ssl); SSl_free(ssl); close(sock); then get out both in Serevr/Client, without waiting for receiving close_notify from either sides. Could that cause memory leak ?? I have called: SSL_shutdown(ssl); SSL_shutdown(ssl); SSl_free(ssl); close(sock); But sometimes I receive return 0 for both call. I do not know why, so I just call one time SSL_shutdown(ssl); SSl_free(ssl); close(sock);
Please help. Thank You TD -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Schwartz Sent: Friday, April 13, 2007 16:19 To: openssl-users@openssl.org Subject: RE: It is Memory leak ?? > > I have Client/Server application using openSSSL. > > Server spin-off threads to handle each client SSL connection. > > I get the following memory leak report when I run valgrind. > > I think I am shutting down/freeing all the memory correctly. > [snip] > > These are empty stacks. It's not a leak because the stacks are in fact > empty. Ack, I just noticed we're talking about 4MB in over 100,00 blocks. The error you pasted is for an empty stack, but probably the objects that own these empty stacks were not properly freed. DS ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]