> 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.
Something wrong is happening. Lots of folks are running apache/openssl
servers for days, weeks, etc., at a time.
If you're seeing memory leaks like you describe, then it is far more
likely that the like is either in your code, or there's a bug in the way
you're calling OpenSSL. Do you get the same growth when openssl isn't
used? Make sure you "xxx_free" every object you "xxx_new".
/r$
--
Rich Salz Chief Security Architect
DataPower Technology http://www.datapower.com
XS40 XML Security Gateway http://www.datapower.com/products/xs40.html
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
