Hi,
I am using openssl (v1.0.0.0e) for my application and when I run valgrind, it
points to memory leaks at some openssl code. Is this really a leak present in
openssl or I need to do something to remove this leak? The following is the
valgrind dump,
==15790== 39,013 (1,288 direct, 37,725
To: openssl-users@openssl.org
Subject: Re: memory leak in openssl
It looks like you did not do an SSL_free when the connection was shut down.
-Kyle H
On Mon, Jun 22, 2009 at 1:16 AM, Vivek Subbaraoviv...@chelsio.com wrote:
Hi,
I am using openssl 0.9.8e that comes along with the linux rhel 5 u3 OS. We
It looks like you did not do an SSL_free when the connection was shut down.
-Kyle H
On Mon, Jun 22, 2009 at 1:16 AM, Vivek Subbaraoviv...@chelsio.com wrote:
Hi,
I am using openssl 0.9.8e that comes along with the linux rhel 5 u3 OS. We
have a client server architecture where both the
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:
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
]
[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
I have a server that I've written using OpenSSL on Mac OS X that has been running for
a few weeks now. Using the leaks command, I am getting the following report:
Leak: 0x003130b0 size=32
0x 0x0030a0c0 0x0030a0e0 0x0030d060
0x 0x1381c88d 0x 0x00010002
Is there a reason you are running mod_ssl and openssl.
One is a complete replacement for the other
You are very confused.
mod_ssl is the glue that adds in OpenSSL to Apache 1.3.x.
In Apache 2.0 mod_ssl is integrated into the apache core.
/r$
--
Rich Salz Chief
In message [EMAIL PROTECTED] on Wed, 13 Aug 2003 18:30:12 +0530, Chandrasekhar R S
[EMAIL PROTECTED] said:
rsr Hello
rsrI have tried to use OpenSSL 0.9.7b with Apache 1.3.28 (with
rsr associated mod_ssl) and have detected significant memory leak.
Do you have the possibility to analyse this
Hello
I have tried to use OpenSSL 0.9.7b with Apache 1.3.28
(with associated
mod_ssl) and have detected significant memory leak.
With the same Apache Server (1.3.28) and with OpenSSL
0.9.6j there is no
memory leak.
Did anyone else also found this observation ? Is
Hi Marko,
Summary:
- IO::Socket::SSL has problems with broken connections
- Crypt::SSL (0.17, includes Net::SSL) still has a memory leak
- Net::SSLeay::get_https works fine
(with own eval()/die() timeout wrapper)
you mentioned having both Crypt-SSLeay and IO-Socket-SSL in your
On Wed, 6 Sep 2000 [EMAIL PROTECTED] wrote:
when using the following combinations I got memory leaks
by sending SSL-requests via LWP objects. I do not
got such problems when using e.g. Net::SSLeay::get_https
directly.
you mentioned having both Crypt-SSLeay and IO-Socket-SSL in your
13 matches
Mail list logo
