RE: Investigating a leak

2005-07-19 Thread David Schwartz
> That'd do it. But if you're doing the loop in that sequence, and > if you have > set non-blocking on the sockets, then instead of polling for the > connection > you can use select or poll (depending on your platform) to wait > for incoming > connection activity, then enter ssl_accept in blocking

Re: Investigating a leak

2005-07-19 Thread Cesc
ely in the real world. > > Regards, > >Simon > > - -- > Simon Edwards > > > > -Original Message- > From: Cesc [mailto:[EMAIL PROTECTED] > Sent: 19 July 2005 09:58 > To: openssl-users@openssl.org > Subject: Re: Investigating a leak > >

RE: Investigating a leak

2005-07-19 Thread Simon Edwards
58 To: openssl-users@openssl.org Subject: Re: Investigating a leak On 7/19/05, Rich Salz <[EMAIL PROTECTED]> wrote: > > Doing this now, but since my app is a server, it never really reaches > > the end, and the leaks build up during its lifetime, which I'd rather > > hoped

Re: Investigating a leak

2005-07-19 Thread Cesc
On 7/19/05, Rich Salz <[EMAIL PROTECTED]> wrote: > > Doing this now, but since my app is a server, it never really reaches > > the end, and the leaks build up during its lifetime, which I'd rather > > hoped could be more than a day or so. As it is now, the process' > > virtual memory size quickly r

Re: Investigating a leak

2005-07-18 Thread Rich Salz
> Doing this now, but since my app is a server, it never really reaches > the end, and the leaks build up during its lifetime, which I'd rather > hoped could be more than a day or so. As it is now, the process' > virtual memory size quickly reaches 3.5 GB, and then malloc() starts > failing. Somet

Re: Investigating a leak

2005-07-18 Thread Axel Andersson
On Jul 18, 2005, at 18:57, Simon Edwards wrote: I don't know if it helps you much, but since the FAQ is a bit cryptic it may help. I've used... ERR_remove_state() ...at the end of each thread. Doing this. Plus... CRYPTO_cleanup_all_ex_data() CONF_modules_free() ERR_free_strings() EVP_c

RE: Investigating a leak

2005-07-18 Thread Simon Edwards
engines or doing anything fancy, so these are probably not a comprehensive list of resource releasing functions. Regards, Simon - -- Simon Edwards -Original Message- From: Amar Desai [mailto:[EMAIL PROTECTED] Sent: 18 July 2005 16:59 To: openssl-users@openssl.org Subject: Re: Investiga

Re: Investigating a leak

2005-07-18 Thread Amar Desai
Yes, You need to call other functions as well. -Amar Axel Andersson wrote: Yes, thank you, indeed I have read that, and I am using ERR_remove_state() at the end of the thread. Looks to me like the other functions should be used before terminating the application, not for per-thread cleanu

Re: Investigating a leak

2005-07-18 Thread Axel Andersson
On Jul 18, 2005, at 14:11, Amar Desai wrote: http://www.openssl.org/support/faq.html Search for the words *memory leak* Yes, thank you, indeed I have read that, and I am using ERR_remove_state() at the end of the thread. Looks to me like the other functions should be used before terminati

Re: Investigating a leak

2005-07-18 Thread Amar Desai
http://www.openssl.org/support/faq.html Search for the words *memory leak* -Amar. Axel Andersson wrote: Hello, I'm investigating a leak in a server application, which I've managed to reduce to a test case which involves OpenSSL and threads. I've put the code up at http://www.zankasoftwar