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
]
[mailto:[EMAIL PROTECTED] On Behalf Of Jason Resch
Sent: Monday, February 06, 2006 7:16 AM
To: openssl-users@openssl.org
Subject: Memory leak in OpenSSL application
Hello everyone,
My company has been working on an SSL enabled server application, and we
have recently encountered a memory leak bug which
Hello everyone,
My company has been working on an SSL enabled server application, and we
have recently encountered a memory leak bug which appears to lead to the
eventual crash of the server. We ran a test having a client application
do nothing but connect to the server application and close
