Hi All
the best thing to track openSSL memory leak (as per my little
understanding) is to have a debug file with Boundschecker and than
provide some traffic and shutdown ur app. In case of leak its caught
by the boundschecker.
Now use some memory allocator (like Buddy Alloc etc...) and than have
> I've been doing some research into this and so far the main
> cause seems
> to be that we were not calling SSL_free after each connection
> closed.
> From what I have gathered, the correct way to cleanup after a
> connection is to call the following functions in this order:
>
> SSL_sh
Do you have session cache enabled? I have had the same suspicion in the
past.
Following links may be usefull.
http://www.openssl.org/docs/ssl/SSL_CTX_set_session_cache_mode.html
http://www.openssl.org/docs/ssl/SSL_CTX_set_timeout.html#
-VJ
-Original Message-
From: [EMAIL PROTECTED]
[mailt
