Hello,
Currently we are seeing below 3 patterns of memory leak issue with Openssl
1.1.1i and 1.1.1k version using address santizer option as below:
Direct leak of 208 byte(s) in 2 object(s) allocated from:
#0 0x9ef57b in __interceptor_malloc
(/usr/local/bin/autoai/custom_binary+0x9ef57b
Hello "d",
On Mon, Jul 20, 2020 at 6:23 PM d via openssl-users <
openssl-users@openssl.org> wrote:
> No memory leakage, if I comment out all SSL related constructs from my
> code.
> Thus, the SSL related code parts seem to be the cause of this leak.
> What is the issue here?
> Makefile:
>
SSL_
No memory leakage, if I comment out all SSL related constructs from my code.
Thus, the SSL related code parts seem to be the cause of this leak.
What is the issue here?
Makefile:
CC=clang
CFLAGS=-g -Wextra -Wall -Werror -pedantic -std=c89 -lssl -fsanitize=address
-fno-omit-frame-pointer
.PHONY:
t; When KTLS is enabled, multiple client's handshake will lead to unexpected
>> eof while reading and data corrupt(possible memory leak).
>>
>> Tested OpenSSL version: master, 3.0.0-alpha1
>> Kernel version: 5.4.43-1-MANJARO
>> Reproduce step(using docker):
>&
Could you please try to re-run the client via Valgrind?
On Fri, Jun 12, 2020 at 7:03 AM Xinzhe Wang wrote:
> When KTLS is enabled, multiple client's handshake will lead to unexpected
> eof while reading and data corrupt(possible memory leak).
>
> Tested OpenSSL version: mas
When KTLS is enabled, multiple client's handshake will lead to unexpected
eof while reading and data corrupt(possible memory leak).
Tested OpenSSL version: master, 3.0.0-alpha1
Kernel version: 5.4.43-1-MANJARO
Reproduce step(using docker):
sudo modprobe tls
git clone https://github.com/op
Hi All,
We are using 1.0.2l version of system openssl that causes memory leak
during a state of congestion. Is this already a known issue?
The same was tested with 1.1.g version of openssl and there was'nt any
leaks. Do anyone know the changes or difference between these 2 versions.
T
* EVP_DigestFinal_ex(mdctx, hash_data.md_value, &hash_data.md_len)*
*Missing reference there for value?*
*Joe*
On Mon, Feb 25, 2019, 09:31 Jakob Bohm via openssl-users <
openssl-users@openssl.org> wrote:
> On 25/02/2019 15:05, Hubert Kario wrote:
> > On Sunday, 24 February 2019 11:34:18 CET pr
On 25/02/2019 15:05, Hubert Kario wrote:
On Sunday, 24 February 2019 11:34:18 CET prithiraj das wrote:
If it helps, sometimes I do get the following errors for the same and
subsequent reboot:
Alignment trap: sh (601) PC=0xb6e008f8 Instr=0x4589c0d7 Address=0x00d7
FSR 0x801
Alignment trap: lo
On Sunday, 24 February 2019 11:34:18 CET prithiraj das wrote:
> If it helps, sometimes I do get the following errors for the same and
> subsequent reboot:
>
> Alignment trap: sh (601) PC=0xb6e008f8 Instr=0x4589c0d7 Address=0x00d7
> FSR 0x801
> Alignment trap: login (584) PC=0xb6e6ab00 Instr=0x
lrigl , openssl-users@openssl.org, Jordan Brown
Betreff: Re: OpenSSL hash memory leak If it
helps, sometimes I do get the following errors for the same and subsequent
reboot:Alignment trap: sh (601) PC=0xb6e008f8 Instr=0x4589c0d7
Address=0x00d7 FSR 0x801Alignment trap: login (584) PC=0xb6e
y to resolve this problem, How do I clear the buff/cache?
>
> On Sun, 24 Feb 2019 at 03:15, Georg Höllrigl
> wrote:
>
>> Hello,
>>
>>
>>
>> I guess you’re not seeing a memory leak, but just normal behaviour of
>> linux file system cache.
>&
here a way to resolve this problem, How do I clear the buff/cache?
On Sun, 24 Feb 2019 at 03:15, Georg Höllrigl wrote:
> Hello,
>
>
>
> I guess you’re not seeing a memory leak, but just normal behaviour of
> linux file system cache.
>
> Buff/cache is keeping files in memor
Hello,
I guess you’re not seeing a memory leak, but just normal behaviour of linux
file system cache.
Buff/cache is keeping files in memory that were least accessed as long as not
needed by other stuff.
You don’t need to free the buffer/cache, because linux does that automatically,
when
e written a code to generate the hash of a file
> in an embeddded device having linux OS and low memory capacity and the
> files are generally of size 44 MB or more. The first time or even the
> second time on some occasions, the hash of any file is successfully
> generated. On the
having linux OS and low memory capacity
> and the files are generally of size 44 MB or more. The first time or
> even the second time on some occasions, the hash of any file is
> successfully generated. On the 3rd or 4th time (possibly due to lack
> of memory/memory leak), the system reboots
generated. On the 3rd or 4th time (possibly due to lack of memory/memory
leak), the system reboots before the hash can be generated. After restart,
the same thing happens when the previous steps are repeated.
The stats below shows the memory usage before and after computing the hash.
*root
My further investigation showed this is a memory leak in my application code
rather than an OpenSSL leak.
Thanks,
Wang
--
Sent from: http://openssl.6102.n7.nabble.com/OpenSSL-User-f3.html
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
My further investigation showed this is a memory leak in application code,
rather than an OpenSSL one.
Thanks,
Wang
--
Sent from: http://openssl.6102.n7.nabble.com/OpenSSL-User-f3.html
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
It appears to be a memory leak in the DNS libraries.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Hi openssl-users,
I found a memory leak in my program that arises from the use of the
BIO_do_connect() function. It seems to be related to how openssl is
interacting with other packages on my system. I observe this behavior
on my Arch Linux machine but not on my Debian Stretch machine. I wrote
Hi,
There seems to be an issue with CMS_decrypt. It seems that if we have
code like this:
CMS_ContentInfo* ci = CMS_encrypt(...);
CMS_decrypt(ci, ...);
CMS_ContentInfo_free(ci);
we leak the X509 certificate's public key. If the call to CMS_decrypt
is commented out, then no leak happens, as the k
Thanks for emailing me! No, I haven’t been hacked :)
I signed up for a spam filtering service called BitBounce. To deliver your
email to my inbox, please click the link below. Thanks!
https://bitbounce.com/pay_bitbounce_fee/1808859525
BitBounce is a product by:
Turing Cloud
Turing-Cloud.com/b
Hi Matt:
Thank you very much for your answer! I did what you told me, and there's no
longer an indication of a memory leak.
Sincerely,
Holger
-Ursprüngliche Nachricht-
Von: Matt Caswell [mailto:m...@openssl.org]
Gesendet: Mittwoch, 22. November 2017 11:50
An: Seiberlich, H
crypto. I've used
> https://wiki.openssl.org/index.php/EVP_Key_Agreement
> as a recipe and wrapped memory allocations into unique_ptrs. The code
> fulfills its purpose of deriving a shared secret, but memory leak detection
> with
> _CrtSetDbgFlag( _CRTDBG
Thanks for emailing me! No, I haven’t been hacked :)
I signed up for a spam filtering service called BitBounce. To deliver your
email to my inbox, please click the link below. Thanks!
https://bitbounce.com/pay_bitbounce_fee/4093641092
BitBounce is a product by:
Turing Cloud
Turing-Cloud.com/b
purpose of deriving a shared secret, but memory leak detection with
_CrtSetDbgFlag( _CRTDBG_ALLOC_MEM_DF | _CRTDBG_LEAK_CHECK_DF );
_CrtSetReportMode( _CRT_WARN, _CRTDBG_MODE_FILE );
_CrtSetReportFile( _CRT_WARN, _CRTDBG_FILE_STDOUT );
produces a warning:
Detected me
This is very important information. Thank you very much, Matt.
I will update the code of my product and test if it resolves my issue. If it
does, I will post my feedback here. Hence other users can aviod the same
issue.
My product is complex and I have other things to do, so it may take a few
da
Thanks again, Rich.
>>>There is something strange with the RSA private key or it’s BN_CONT
object.
>>>Are you sure that you are properly releasing all OpenSSL objecdts in your
code?
My application is a server. When it is initialized it calls RSA_new() to
allocate a RSA object. When the serv
On 08/11/17 09:47, Wang wrote:
> Hello Matt,
>
> Thank you for trying to help.
>
Is this the "bottom" of the OpenSSL stack? i.e. your application calls
RSA_private_decrypt() directly?
> Yes, it does.
>
Do you share a single RSA object across multiple threads?
> Yes, my applic
Hello Matt,
Thank you for trying to help.
>>>Is this the "bottom" of the OpenSSL stack? i.e. your application calls
>>>RSA_private_decrypt() directly?
Yes, it does.
>>>Do you share a single RSA object across multiple threads?
Yes, my application shares a single RSA object across many concurre
There is something strange with the RSA private key or it’s BN_CONT object.
Are you sure that you are properly releasing all OpenSSL objecdts in your code?
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
On 07/11/17 10:01, Wang wrote:
> Hello Rich,
>
> Thank you for trying to help.
>
> My product is running on Linux. The following leak was detected by Valgrind.
> Valgrind only reportes
> the leak in threaded mode. I run 'top' on linux to monitor the memory usage
> of my product. I can see the
Hello Rich,
Thank you for trying to help.
My product is running on Linux. The following leak was detected by Valgrind.
Valgrind only reportes
the leak in threaded mode. I run 'top' on linux to monitor the memory usage
of my product. I can see the memory usage increases quickly.
==9721== 520 byt
➢
http://openssl.6102.n7.nabble.com/Memory-issues-with-ssl-handshake-td20851.html#a20854.
➢ Don't understand why this issue is not encountered by other users and why
it
has not been fixed for so many years.
The first part answer the second. It is not encountered by others, so
The product can be build in threaded or non-threaded mode. The memory leak
can be detected only in threaded mode. Hence I think I hit the same issue
reported by Thomas in 2012.
"One thing I noticed is that all goes well if I cause the code to
run sequentially (e.g. cause requests to com
Hello, The memory usage of one of our OpenSSL applications increases
quickly.Valgrind detects the only possible leak below. We are using OpenSSL
1.0.2k. ==9721== 520 bytes in 1 blocks are indirectly lost in loss record
1,178 of1,294 ==9721==at 0x4A0817C: malloc (vg_replace_malloc.c:298)
==9721=
Hello,
I got an application that establishes an TLS connection for communication.
While the communication works, I run into a memory leak that originates from
CRYPTO_malloc. I tried to search for proper OpenSSL shutdown and related
issues, but my tries did not affect the leak. Here is the ASAN
> I am using openssl 1.0.2 to do some ssl connection, now I am facing
> some memory leak issue.
>
> ssl = SSL_new(m_ctx);
> sbio = BIO_new_socket(server, BIO_NOCLOSE);
> SSL_set_bio(ssl,sbio,sbio);
>
>
> SSL_connect()
> ...
>
> //After handle, release resou
If you used BIO_NOCLOSE then you have to close the BIO.
Yes, after shutdown is done, call SSL_free()
___
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Hi.
I am using openssl 1.0.2 to do some ssl connection, now I am facing
some memory leak issue.
ssl = SSL_new(m_ctx);
sbio = BIO_new_socket(server, BIO_NOCLOSE);
SSL_set_bio(ssl,sbio,sbio);
SSL_connect()
...
//After handle, release resource
if(ssl)
SSL_shutdown(ssl);
Now I have some
Hello Openssl Users,
Currently we are facing a memory leak issue in the following scenario.
We are allocating dynamic memory to a appctx and we are setting this appctx
to the session using the function
SSL_SESSION_set_app_data().
My understanding is that, this appctx will be updated as part of
On 03/12/14 10:34, T@Run..! Polisetty wrote:
> Hai All,
>
>We are using Openssl for DTLS Negotiations. When we run the Valgrind
> with this setup. We are finding some major loss of memory at one place.
>
>
> ==23871== 4,224 (1,056 direct, 3,168 indirect) bytes in 3 blocks are
On Wed, Dec 03, 2014 at 04:04:16PM +0530, T@Run..! Polisetty wrote:
> Hai All,
>
>We are using Openssl for DTLS Negotiations. When we run the Valgrind
> with this setup. We are finding some major loss of memory at one place.
Can you check with a current git version? There have b
| 585.421.5565
From: owner-openssl-us...@openssl.org [owner-openssl-us...@openssl.org] on
behalf of Dr. Stephen Henson [st...@openssl.org]
Sent: Friday, November 21, 2014 1:40 PM
To: openssl-users@openssl.org
Subject: Re: Small memory leak on multithreaded
ollect
obsolete classes either.
> On 21-11-2014 23:23, Viktor Dukhovni wrote:
>> On Fri, Nov 21, 2014 at 04:13:58PM -0500, Jeffrey Walton wrote:
>>>> A fixed amount of memory that is not deallocated and is independent
>>>> of the number of operations performed, is
On Sun, Nov 23, 2014 at 10:56:41PM +0100, Jakob Bohm wrote:
> >Unloading of shared libraries is generally unsafe. Loading and
> >unloading of pure of Java packages may work well enough, but I
> >would [not] expect a Java runtime that unloads native libraries to stay
> >running for very long.
>
>
On 21-11-2014 23:23, Viktor Dukhovni wrote:
On Fri, Nov 21, 2014 at 04:13:58PM -0500, Jeffrey Walton wrote:
A fixed amount of memory that is not deallocated and is independent
of the number of operations performed, is NOT a memory leak.
Languages like Java and C# can continuously load and
g]
Sent: Friday, November 21, 2014 1:40 PM
To: openssl-users@openssl.org
Subject: Re: Small memory leak on multithreaded server
On Fri, Nov 21, 2014, Barbe, Charles wrote:
> Yes... sorry, forgot to include this part of my shutdown sequence. One thing
> I am noticing is that I do not call X40
On Fri, Nov 21, 2014 at 04:13:58PM -0500, Jeffrey Walton wrote:
> > A fixed amount of memory that is not deallocated and is independent
> > of the number of operations performed, is NOT a memory leak.
>
> Languages like Java and C# can continuously load and unload a library
> A fixed amount of memory that is not deallocated and is independent
> of the number of operations performed, is NOT a memory leak.
Languages like Java and C# can continuously load and unload a library.
You will see a growth in memory usage because the memory is not
reclaimed.
> Libr
On Fri, Nov 21, 2014, Barbe, Charles wrote:
> Yes... sorry, forgot to include this part of my shutdown sequence. One thing
> I am noticing is that I do not call X409_free on my certs. I even have a
> comment in my code saying that I am not freeing them because I think they
> will be freed when the
: Re: Small memory leak on multithreaded server
On Fri, Nov 21, 2014, Barbe, Charles wrote:
> Thanks for the response... here is the code that runs when my connection
> closes:
>
> void OpensslConnection::cleanup()
> {
> if(ssl != NULL)
> {
> if(isConnected
On Fri, Nov 21, 2014, Barbe, Charles wrote:
> Thanks for the response... here is the code that runs when my connection
> closes:
>
> void OpensslConnection::cleanup()
> {
> if(ssl != NULL)
> {
> if(isConnected)
> {
> while(SSL_shutdown(ssl) == 0)
>
On Fri, Nov 21, 2014 at 03:21:47PM +, Barbe, Charles wrote:
> What looks suspicious to me is the calls to "x509v3_cache_extensions"
> that are in the traces below. This implies to me that openssl is
> caching something. How do I ask it to clear that cache? If i need
> to augment the library to
r-openssl-us...@openssl.org [owner-openssl-us...@openssl.org] on
behalf of Dr. Stephen Henson [st...@openssl.org]
Sent: Thursday, November 20, 2014 9:50 PM
To: openssl-users@openssl.org
Subject: Re: Small memory leak on multithreaded server
On Thu, Nov 20, 2014, Barbe, Charles wrote:
> Hello,
tes).
From: owner-openssl-us...@openssl.org [owner-openssl-us...@openssl.org] on
behalf of Jeffrey Walton [noloa...@gmail.com]
Sent: Thursday, November 20, 2014 6:03 PM
To: OpenSSL Users List
Subject: Re: Small memory leak on multithreaded server
Any help would be apprecia
On Fri, Nov 21, 2014 at 02:26:45PM +, Barbe, Charles wrote:
> static void
> openSslShutdown ()
> {
You could try adding:
ENGINE_cleanup();
if that helps.
> CONF_modules_free();
> ERR_remove_state(0);
> CONF_modules_unload(1);
> ERR_free_strings();
> EVP_cl
-us...@openssl.org [owner-openssl-us...@openssl.org] on
behalf of Jeffrey Walton [noloa...@gmail.com]
Sent: Thursday, November 20, 2014 6:03 PM
To: OpenSSL Users List
Subject: Re: Small memory leak on multithreaded server
> Any help would be appreciated.
This could be one of two problems. Fir
: Re: Small memory leak on multithreaded server
On Thu, Nov 20, 2014 at 10:19:32PM +, Barbe, Charles wrote:
> I can do any combination of steps 2,3 and 4 above (ie. leave some
> of them out) and I always get the same amount of memory left over
> after I shut down my application. I bel
On Thu, Nov 20, 2014, Barbe, Charles wrote:
> Hello,
>
> I have noticed a small and consistent memory leak in my multithreaded openssl
> server and am wondering if somebody can help me figure out what I need to do
> to free it when my application closes. I am on OpenSSL version
20 blocks filter
> down to 1 of 5 root stack traces. The stack traces are:
A fixed amount of memory that is not deallocated and is independent
of the number of operations performed, is NOT a memory leak.
Librariers to allocate memory for the lifetime of the process during
one time initializat
> Any help would be appreciated.
This could be one of two problems. First, it could be an issue with
your code and the way you handle cleanup. To help diagnose this,
please show us your cleanup code.
Second, it could be the memory leak from the compression methods. This
is a well known prob
Hello,
I have noticed a small and consistent memory leak in my multithreaded openssl
server and am wondering if somebody can help me figure out what I need to do to
free it when my application closes. I am on OpenSSL version 1.0.1j. Here's how
I reproduce the leak:
1) Start up my ser
I am not a 100% sure but I think s->s3 control structure is not being freed in
case of app enabling OPENSSL_NO_SSL3 patch code. Ssl23_get_client_hello will
return with s->method==NULL. SSL_free will skip over ssl3_free. 0.9.8zc might
be leaking more than just s->s3. ( may be dgst msgs). Please c
We are testing our application (that uses OpenSSL for FTPS) to check the
memory leak over time(continuous FTPS upload is performed for about 12
hours).
We observed that the memory consumed by the process is reduced(about 3MB)
after 6 mins.
Kindly let us know if it is related to the SSL session
We observed that sometimes SSL_Shudown() is not returning success.
If the cache is maintained, will the API fail.
--
View this message in context:
http://openssl.6102.n7.nabble.com/openssl-memory-leak-tp52311p52361.html
Sent from the OpenSSL - User mailing list archive at Nabble.com
return true;
}
Kindly let us know if any other additional APIs need to be called to free
the SSL session completely.
We found that SSL session is maintained in the cache after the first upload.
i.e about 1000KB of memory is increased after first SSL Session and the
memory is not compl
The openssl source package includes a generic server (s_server) and client
(s_client).
My first suspect when something has a memory leak with SSL connections only is
to check whether SSL contexts returned by SSL_new() always get cleaned up later
by calling SSL_free()...
Andrew
-Original
We are using Openssl for FTPS connections. We are facing issues with memory
leak.
Kindly let us know if there is sample code.
--
View this message in context:
http://openssl.6102.n7.nabble.com/openssl-memory-leak-tp52311.html
Sent from the OpenSSL - User mailing list archive at Nabble.com
I found my memory leak origin. I didn't free an X509 object when I called
SSL_get_peer_certificate function (missing X509_free() call). Hope it will be
useful for others
Cheers!!
From: hicham55...@hotmail.com
To: openssl-users@openssl.org
Subject: RE: Memory leak in ssl3_get_server_certif
Well, I found out where it's defined. It's a MACRO definition (
IMPLEMENT_ASN1_ENCODE_FUNCTIONS_fname ). I'm still investigating the leak
Regards
From: hicham55...@hotmail.com
To: openssl-users@openssl.org
Subject: Memory leak in ssl3_get_server_certificate
Date: Thu
Hello all,
I found a memory leak when using ssl_connect function. Bellow the valgrind
trace:
==12028== 37,600 (1,040 direct, 36,560 indirect) bytes in 10 blocks are
definitely lost in loss record 12 of 27
==12028==at 0x40053C0: malloc (vg_replace_malloc.c:149)
==12028==by 0x4185C8E
On Tue, Feb 18, 2014, Varma Dantuluri wrote:
> Thanks Steve for the response. Given the current way it is done in
> OpenSSL-1.0.1f, what is the right thing for the application to do? Should
> the application be using a static EC_KEY for each of the curves that are
> supported?
>
For 1.0.1f the c
:
> On Thu, Feb 13, 2014, Varma Dantuluri wrote:
>
> > In OpenSSL-1.0.1f, in 'ssl3_send_server_key_exchange' function, when all
> > the below conditions are true, there is a potential memory leak.
> >
> > 1) 'type & SSL_kEECDH' is true, (ie the
On Thu, Feb 13, 2014, Varma Dantuluri wrote:
> In OpenSSL-1.0.1f, in 'ssl3_send_server_key_exchange' function, when all
> the below conditions are true, there is a potential memory leak.
>
> 1) 'type & SSL_kEECDH' is true, (ie the key exchange is ephemeral ec
In OpenSSL-1.0.1f, in 'ssl3_send_server_key_exchange' function, when all
the below conditions are true, there is a potential memory leak.
1) 'type & SSL_kEECDH' is true, (ie the key exchange is ephemeral ecdh)
2) 'ecdhp == NULL' && 's->cert->e
need to cleanup up all memory used by
a single SSL session at session closure.
Awaiting your kind help.
Rajib
NB: I had earlier (19/1/2012) posted a similar problem
(http://openssl.6102.n7.nabble.com/Memory-leak-in-openssl-td28304.html) but
didn't got any response.
--
View this messa
Hi all,
I am only using SSL for handling TLS/SSL handshakes in libcurl. I am
encountering the memory leaks described in this defect:
http://rt.openssl.org/Ticket/Display.html?id=2561&user=guest&pass=guest
which seem to be caused by not cleaning up the compression methods
stuff.
Does anyone know
Ahoy the list. I'm seeing a memory leak using openssl 0.9.8h (0x0090808f 28
May 2008) on Solaris 5.10 from calling SSL_connect() and am trying to nail
down the cause. I'm sure it's a PEBKAC error, but can't spot it.
The leak was identified by watching the process me
Hi,
I am using x509_dup to create a duplicate certificate. Once I am done with my
work, I use X509_free to free the duplicate certificate. But when I run my code
with valgrind, it reports of some leaks. The following is the valgrind stack
trace,
==3845== 408 (72 direct, 336 indirect) bytes
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 i
On Wed, Dec 21, 2011 at 1:26 PM, nandan shantharaj wrote:
> Hi All,
> SSL_CTX_load_verify_locations() is causing memory leak in my
> application. Folowing is the function trace.
>
> 262 1072 bytes leaked in 4 blocks (2.25% of all bytes leaked)
> 263 These range in si
Hi All,
SSL_CTX_load_verify_locations() is causing memory leak in my
application. Folowing is the function trace.
262 1072 bytes leaked in 4 blocks (2.25% of all bytes leaked)
263 These range in size from 268 to 268 bytes and are allocated
264 #0 0x83ffefb9b6b8 in
didn't use the "X509_OBJECT_free_contents()" to free the contents of the
returned object "obj". It seems this is the cause of the memory leak. By adding
"X509_OBJECT_free_contents(&obj)" function, the Purify does not report any
memory leaks.
Thanks
Bob
-Original Message
On Fri, Jun 24, 2011, Yan, Bob wrote:
Hi,
I have used IBM purify to check my test program which invokes openssl
library. There are some memory leaks reported by Purify, please see
below. Could somebody point to me from which function those leaks were
generated, and how to avoid those leak
On Behalf Of t...@terralogic.net
> Sent: Friday, June 24, 2011 4:52 PM
> To: openssl-users@openssl.org
> Subject: Re: Question regarding to memory leak
>
> I have suggested this before. Write your own memtools.
>
>
> http://www.terralogic.net/developer/developer.html
>
On Fri, Jun 24, 2011, Yan, Bob wrote:
> Hi,
>
> I have used IBM purify to check my test program which invokes openssl
> library. There are some memory leaks reported by Purify, please see below.
> Could somebody point to me from which function those leaks were generated,
> and how to avoid tho
To: openssl-users@openssl.org
Subject: Re: Question regarding to memory leak
I have suggested this before. Write your own memtools.
http://www.terralogic.net/developer/developer.html
I tossed up a couple poor boy examples.
Note the calls:
struct pfa_ControlBlock chain1 = { ipfa_ControlBlock
I have suggested this before. Write your own memtools.
http://www.terralogic.net/developer/developer.html
I tossed up a couple poor boy examples.
Note the calls:
struct pfa_ControlBlock chain1 = { ipfa_ControlBlock }
, chain2 = { ipfa_ControlBlock };
pfa_Init( &chain1,
As a general comment not all memory leaks reported by these tools are
a bad thing. I often write code that has these type of leaks on
purpose for performance reasons. For example a function that is
called often and malloc's memory ... rather than malloc and free each
time (causing context swi
Hi,
I have used IBM purify to check my test program which invokes openssl library.
There are some memory leaks reported by Purify, please see below. Could
somebody point to me from which function those leaks were generated, and how to
avoid those leaks? Thanks, Bob
MLK: 1104 bytes le
dear all:
No one encountered this problem?
>From: ""
>Reply-To: openssl-users@openssl.org
>To: openssl-users@openssl.org
>Subject: about ssl_accept and memory leak
>Date:Mon, 27 Dec 2010 13:38:49 +0800
>
>Dear openssl-users£¬
>
>
> When using
Dear openssl-users£¬
When using the openssl and found a large number of connections during the
establishment of the memory has been growing closed, the test found that when
the
memory is increased to 317548K, the not increased, the initial memory, only a
few
K, very strange.
why? How can I
Stop opressing women. Girls should NOT be married at puberty to men, men should
NOT be happy for the rest of their lives.
--- On Mon, 12/27/10, lizhiping wrote:
From: lizhiping
Subject: about ssl_accept and memory leak
To: "openssl-users"
Date: Monday, December 27, 201
Dear openssl-users，
When using the openssl and found a large number of connections during the
establishment of the memory has been growing closed, the test found that when
the memory is increased to 317548K, the not increased, the initial memory, only
a few K, very strange.
why? How can I res
Hello,
We have a firewall acting as a reverse proxy(server) doing SSL offload and we
are seeing a memory leak in x509_name_ex_new.
We are using OpenSSL 0.9.8l and we ran the OpenSSL's builtin memory leak
checker, dumped the results using CRYPTO_mem_leaks_fp and found several leaks
reported
Steve & Mounir,
Thanks a lot for answering my questions.
Stuart
- Original Message
From: Dr. Stephen Henson
To: openssl-users@openssl.org
Sent: Mon, April 19, 2010 4:38:14 PM
Subject: Re: possible user error / memory leak using RSA_new() and RSA_free();
On Mon, Apr 19,
On Mon, Apr 19, 2010, Stuart Weatherby wrote:
> Thanks Steve,
>
> After commenting out lines 24 & 25 there is still unfree'd memory:
>
http://www.openssl.org/support/faq.html#PROG13
Steve.
--
Dr Stephen N. Henson. OpenSSL project core developer.
Commercial tech support now available see: http:
enssl.org
Sent: Mon, April 19, 2010 3:12:53 PM
Subject: Re: possible user error / memory leak using RSA_new() and RSA_free();
On Mon, Apr 19, 2010, Stuart Weatherby wrote:
> Hi List,
>
> I am trying to figure out why there is a memory leak using RSA_new & RSA_free:
> Below is
1 - 100 of 235 matches
Mail list logo
