Hi, On Thu, Dec 05, 2013 at 02:01:05PM +0100, arno.oderm...@ch.schindler.com wrote: > thank you. Yes, it is acceptable. > From our point of view, it still seems, memory not to be released > properly, when a disconnection script has been run. > In our environment with O-VPN 2.3.2, when we start to disconnect large > amounts of client sessions, using the disconnect script, memory seems not > to become freed, and therefore can not be re-used by other sessions. This > is a problem, since the app might run out of memory again.
"Not being free()ed" and "not being returned to the OS" are two different
things. So unless you see a memory increase on reconnect, I'd guess it
is "memory is free()ed, but due to whatever reasons not returned to the
OS by the malloc library".
(In your case, it might be worthwile to investigate linking with PolarSSL
instead of OpenSSL, as the memory footprint is *much* smaller, from the
numbers Brad posted)
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgp8Yp5olIFJM.pgp
Description: PGP signature
