the openssl library version is 1.0.1c, the operation system is debian linux.
On Fri, Oct 26, 2012 at 8:05 PM, Zhuang Yuyao wrote:
> Hi,
>
> I'm testing loading a large CRL file into a X509_CRL structure then
> free it. but after X509_CRL_free, there are still some mysterious
> memory consumption.
On Nov 7, 2009, at 2:50 PM, barcaroller wrote:
I'm getting some memory leaks when I use OpenSSL. I was not able to
get rid
of these leaks, even when I use EVP_cleanup() and ERR_free_strings()
at the
end of my program.
[]
==27769== 24 bytes in 1 blocks are still reachable in loss r
I solved te problem by calling ERR_remove_state(0) for every thread which
uses a SSL connection.
--
View this message in context:
http://www.nabble.com/Memory-Leaks-on-every-connection-tp22805904p22832875.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
_
Lars,
I assume you are running this inside a loop inside of main() and that is
how you can tell there is a leak?
Joe
Lars Uhlmann wrote:
Please reference http://www.openssl.org/support/faq.html#PROG13 --
> "I think I've detected a memory leak, is this a bug?"
Thanks!
It doesn't matte
On Mon, Feb 05, 2007, Lars Uhlmann wrote:
> >Please reference http://www.openssl.org/support/faq.html#PROG13 --
> > "I think I've detected a memory leak, is this a bug?"
> >
> >Thanks!
>
> It doesn't matter if I call those cleaning functions, the leaks are
> still there.
>
> /* --- cut here ---
> > Please reference http://www.openssl.org/support/faq.html#PROG13 --
> > "I think I've detected a memory leak, is this a bug?"
> >
> > Thanks!
>
> It doesn't matter if I call those cleaning functions, the leaks are
> still there.
In most cases the cause of an apparent memory leak is an Open
Please reference http://www.openssl.org/support/faq.html#PROG13 --
> "I think I've detected a memory leak, is this a bug?"
Thanks!
It doesn't matter if I call those cleaning functions, the leaks are
still there.
/* --- cut here --- */
#include
#include
#include
#include
#include
int ma
Please reference http://www.openssl.org/support/faq.html#PROG13 -- "I
think I've detected a memory leak, is this a bug?"
Thanks!
-Kyle H
On 2/4/07, Lars Uhlmann <[EMAIL PROTECTED]> wrote:
I wrote a little test program to speak HTTP over SSL (so called
HTTPS ;-). The code (nicely formatted and
Steffen Lips wrote:
Hi everybody,
we have written a server application wich uses openssl. now we found
out, that memory increases rapidly.
Then we found out, that there are memory leaks in openssl. so try this
little program:
#include
#include
#include
void *crypto_mem_leak_cb(unsigned
> The way I normally trace this stuff is to run it under a debugger first to
> get the addresses of leaks then a second time with conditional breakpoints
> added at those points so that when that same address is allocated it is
> possible to do a stack trace to see the precise cause.
>
> That ex_da
On Thu, Jul 03, 2003, Walter Proseilo wrote:
> I'm currently using openssl to provide TLS support for our software. We have
> our own networking implemtation using the Linux (unix) networking commands.
> This deos error handling, buffering, blocking etc.
>
> The TLS implimentation uses the
You might also try ERR_free_strings() if you ever called
ERR_load_crypto_strings() and/or SSL_load_error_strings(). That cleared up
my memory leaks.
Regards,
Aram Perez
Dr. Stephen Henson wrote:
> On Tue, Mar 18, 2003, Dmitry Sokolov wrote:
>
>> Code:
>> ---8<--
On Tue, Mar 18, 2003, Dmitry Sokolov wrote:
> Code:
> ---8<---
> DSA *d = DSA_new();
> DSA_free( d );
> ---8<---
>
> gives leaks:
> ---8<---
> Detected memory leaks!
> Dumping objects ->
> {57} normal
On Thu, Jan 09, 2003, Aslam wrote:
> Hi,
>
> I used to do openssl memory leaks checking using following code under
> openssl-0.9.6x:
>
> int main(int argc, char* argv[])
> {
> CRYPTO_malloc_debug_init();
> CRYPTO_dbg_set_options(V_CRYPTO_MDEBUG_ALL);
> CRYPTO_mem_ctrl(CRYPTO_ME
In message <002b01c283f5$917bc8b0$[EMAIL PROTECTED]> on Mon, 4 Nov 2002 18:30:24
+0700, "Wadim S. Dicke" <[EMAIL PROTECTED]> said:
dicke> Can anybody help me with the following problem. When I compile OpenSSL
dicke> for linux-elf, 'make' passes without any errors, but when I try to do 'make
dic
There are still a few memory leaks that can't be cleaned up without
modifying openssl. It is only a few bytes, but they're real. Tee development
team has said they are aware of it (check the archives) but it is a
relatively low priority item.
==
Greg Stark
[EMAIL PROTECTED]
==
Sometimes the leaks reported by boundscheker are not really leaks
Check if there are leaks reported in the ouput window-debug tab when
the app exits
- Original Message -
From: "White Jack" <[EMAIL PROTECTED]>
Date: Tuesday, September 4, 2001 11:21 pm
Subject: memory leaks
> hi,
> I used
On Thu, 2 Aug 2001 20:17:52 +0100, "Mike Scriven" <[EMAIL PROTECTED]>
wrote:
>I've written a Windows app. using OpenSSL and I'm getting memory
>leaks when I close it, even if I haven't connected a socket.
I'm no expert, but I've been reading the man pages a lot... so here are
my thoughts.
>At
On Friday 27 July 2001 10:04 am, you wrote:
> Hi all.
>
> I followed instructions in
> http://marc.theaimsgroup.com/?l=openssl-users&m=99494629705968&w=2
> to find memory leaks in my application.
>
> The output generated by CRYPTO_mem_leaks_fp (as show below) tells me
> that 899 bytes were leaked
t; <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, April 25, 2001 12:29 PM
Subject: Re: Memory leaks
> Hi Greg,
>
> I haven't checked yet, but it doesn't seem to be the same problem. The
code
> I've written init
]
_
- Original Message -
From: "Gustavo Badauy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 25, 2001 9:11 AM
Subject: Re: Memory leaks
> Hi Tat,
>
> it's 972 bytes. It's not little when we are thinking on
nssl-users@openssl.org/msg11445.html).
_
Greg Stark
Ethentica, Inc.
[EMAIL PROTECTED]
_
- Original Message -
From: "Harald Koch" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 19, 2001 4
leaks reported by tools ususally include a lot of potential ones. That
means, in the error conditions, the leaking will be possible. If you
believe it, you should
make every possible means to check all parametes before you make call to
that function.
Heyun Zheng
[EMAIL PROTECTED]
-Ori
I have used those openssl functions you mentioned and did not see any
leaking.
I have looked your code carefully and do not see any wrong either.
Heyun Zheng
[EMAIL PROTECTED]
-Original Message-
From: aslam [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 18, 2001 4:27 PM
To: opens
ent: Friday, June 30, 2000 4:52
AMTo: [EMAIL PROTECTED]Subject: RE: memory leaks
in openssl - urgent...
Hi all
I have also been receiving numerous copies of
each message posted for the 24 hours...
I just wanted to add my BoundsChecker printout
to the pool, I am also trying to el
Hi all
I have also been receiving numerous copies of each message posted for the 24 hours...
I just wanted to add my BoundsChecker printout to the pool, I am also trying to eliminate memory leaks from my app. If I find something out I will let you know.
BTW Arora : i am calling the same function
On Thu, Jun 29, 2000 at 11:13:43PM +0200, Richard Levitte - VMS Whacker wrote:
> Hey!
>
> Repeating your message x times doesn't solve anything. On the
> contrary, it may piss people off, and then I'll just say "happy
> isolation!" to you.
I got this message twice... but I'm going to assume it
On Thu, 29 Jun 2000, Richard Levitte - VMS Whacker wrote:
> Hey!
>
> Repeating your message x times doesn't solve anything. On the
> contrary, it may piss people off, and then I'll just say "happy
> isolation!" to you.
I have received yours about 8 times too - looks like a mailing list
burp.
Title: RE: memory leaks in openssl - urgent... latest ERR_remove_state() reduced some of them but not all...
hello
i would suggest u all to replace the ERR_remove_state() in ur
crypti\err.c file, with the foll. one(if don't have the latest one). it would reduce many of ur memory
Title: RE: memory leaks in openssl - urgent...
hello
i tried to build my application with the latest function ERR_remove_state() from the snapshot from openssl site , as suggested , but still the memory leak remains as such..the new function looks like
void ERR_remove_state(unsigned long
> Arora Meenakshi wrote:
>
> hello
> Please reply to this mail if anyone has any suggestions. i have posted
> this question a lot of times but no success so i am again giving it a
> try.
>
> i am running my openssl code in bounds checker & i am getting the
> memory leaks in*CRYPTO_malloc(int num
Title: RE: memory leaks in openssl - urgent...
hello
Pls. if u could tell me which function should i call to free SSL_METHOD structure???
thanx
meenakshi
-Original Message-
From: Taral [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 29, 2000 2:30 PM
To: [EMAIL PROTECTED]
Cc
Hey!
Repeating your message x times doesn't solve anything. On the
contrary, it may piss people off, and then I'll just say "happy
isolation!" to you.
--
Richard Levitte \ Spannvägen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken \ S-168 35 BROMMA \ T: +46-8-26 52 47
Redakteur@Stacken \
On 29 Jun, Arora Meenakshi wrote:
> hello
> just a suggestion..
> i have found that even if i call the
> ctx = SSL_CTX_new (meth);
> followed by no other calls to openssl & then clean up the stuff
> i still get this memory leak
> meenakshi
Did you free the SSL_METHOD structure?
Title: RE: memory leaks in openssl - urgent...
i don't think i repeated my question (x > 1) times , yes i asked the same question a week back , waited for a week , no response & then thought of reposting with a clear indication that's its already posted
did i
Title: RE: memory leaks in openssl - urgent...
hello
just a suggestion..
i have found that even if i call the
ctx = SSL_CTX_new (meth);
followed by no other calls to openssl & then clean up the stuff
i still get this memory leak
meenakshi
-Original Message-
I'm having the same problems and I can't seem to get to the snapshot.
I keep getting an error "500 Illegal PORT Command".
> -Original Message-
> From: Michal Trojnara [mailto:[EMAIL PROTECTED]]
> Sent: Monday, May 01, 2000 6:16 PM
> To: [EMAIL PROTECTED]
Odpowiedz automatyczna:
Do 5 maja przebywam na zasluzonym urlopie.
W pilnych sprawach prosze o kontakt z Kamilem Kilinskim.
Z powazaniem,
Michal Trojnara
>>> "[EMAIL PROTECTED]" 05/01/00 21:51 >>>
Amit Chopra <[EMAIL PROTECTED]>:
> I had reported some leaks some time back, but got no re
Amit Chopra <[EMAIL PROTECTED]>:
> I had reported some leaks some time back, but got no response from the
> mailing list.
>
> OpenSSL 0.9.4 leaks 332 bytes for ERR_STATE struct allocated while doing
> SSL_read.
> ERR_get_state [err.c:561]
> => ret=(ERR_STATE *)Malloc(siz
Dr Stephen Henson <[EMAIL PROTECTED]>:
> Bodo Moeller:
>> [EMAIL PROTECTED]:
>>> VC6.0 detected memory leaks in the following code! And the code do
>>> only PEM_read_bio_PrivateKey()!!
>> You should free your OpenSSL objects (pKey, in) *before* freeing
>> the library-internal stuff (EVP_cleanup(
Bodo Moeller wrote:
>
> [EMAIL PROTECTED]:
>
> > VC6.0 detected memory leaks in the following code! And the code do only
>PEM_read_bio_PrivateKey()!!
> >
> > When I enabled the OpenSSL_add_ssl_algorithms() and the PEM_read_bio_PrivateKey
> > () finished sucessful, there is no memory leaks.
> >
[EMAIL PROTECTED]:
> VC6.0 detected memory leaks in the following code! And the code do only
>PEM_read_bio_PrivateKey()!!
>
> When I enabled the OpenSSL_add_ssl_algorithms() and the PEM_read_bio_PrivateKey
> () finished sucessful, there is no memory leaks.
> But when I disable(comment out) the
ks( ); /* win32 specific */
#endif
}
- Original Message -
From: Bodo Moeller <[EMAIL PROTECTED]>
To: Richard Dykiel <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, March 16, 2000 5:18 PM
Subject: Re: memory leaks in SSLeay_add_all_algorithms?
> On Thu, M
On Thu, Mar 16, 2000 at 05:31:50PM -0500, Richard Dykiel wrote:
> Tried it, now I have less leaks:
> Detected memory leaks!
> Dumping objects ->
> {3409} normal block at 0x0090A8D0, 512 bytes long.
> Data: <> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> {2596} normal block a
90 00 6C B5 40 00 EF B5 40 00 41 00 00 00
Object dump complete.
This will make it easier for me to identify my leaks.
Thanks.
- Original Message -
From: Bodo Moeller <[EMAIL PROTECTED]>
To: Richard Dykiel <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, March 16,
Richard Dykiel <[EMAIL PROTECTED]>:
> I tried the cleanup calls advised by Bodo, it works fine so far as OpenSSL
> is concerned; I tested the CRYPTO mem debug functions & I am now confident
> they'll spot my bugs.
>
> However I still have the following leaks reported by Win32's debugging
> tools
- Original Message - > Anyway, saying that OpenSSL doesn't leak *in
debug mode* is not
> entirely true. The memory debugging code does create at least one
> hash table and at most two, and it never free's them. I've been
> pondering adding a CRYPTO_mem_cleanup() or something like that,
dykiel> However I still have the following leaks reported by Win32's
dykiel> debugging tools:
Yup, those are from the lhash table that the memory debugging routines
create.
dykiel> Detected memory leaks!
dykiel> Dumping objects ->
I would assume that this is a block of pointers to struct lhash_
_CrtDumpMemoryLeaks( ); /* win32 specific */
#endif
}
- Original Message -
From: Bodo Moeller <[EMAIL PROTECTED]>
To: Richard Dykiel <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Wednesday, March 15, 2000 8:11 PM
Subject: Re: memory leaks in SSLeay_add_all_algorith
Richard Dykiel <[EMAIL PROTECTED]>:
> Hello, the simple piece of code below results in "4243 bytes leaked
> in 280 chunks" as reported by the CRYPTO debug memory functions.
>
> Most leaks are caused by the call to SSLeay_add_all_algorithms.
[...]
> Am I missing some mandatory cleanup call?
Yes
dykiel> Hello, the simple piece of code below results in "4243 bytes leaked in 280
chunks" as reported by the CRYPTO debug memory functions.
dykiel>
dykiel> Most leaks are caused by the call to SSLeay_add_all_algorithms.
No surprise there. That function, and the functions called by it,
registe
gic <[EMAIL PROTECTED]>:
> I was developing an SSL client (with openssl-0.9.3a)
> and found memory leaks when using RC4-MD5 (1024/128 bits).
> HOWEVER, when I switched to "EXP-RC4-MD5" (512/40 bits),
> there are NO leaks.
>
> The best way to reproduce the leaks is to run 's_time'
> for a long ti
52 matches
Mail list logo
