Dear Brad, 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.
freundlich grüsst, kind regards, _________________________ _________________________ _________________________ _________________________ _________________________ ________________ Arno Odermatt Phone +41414454053 arno.oderm...@ch.schindler.com Schindler Elevator Ltd. | Corporate Research & Development | CRD/CO-BAT Zugerstr. 13 | CH-6030 Ebikon, Switzerland http://www.schindler.com _________________________ _________________________ _________________________ _________________________ _________________________ ________________ Please consider your environment. Schindler supports sustainable urban development with safe, reliable and ecologically sound mobility solutions. From: Brad Zhang <hebei5...@gmail.com> To: Gert Doering <g...@greenie.muc.de>, arno.oderm...@ch.schindler.com, Cc: openvpn-devel@lists.sourceforge.net List-Post: openvpn-devel@lists.sourceforge.net Date: 05.12.2013 09:11 Subject: Re: [Openvpn-devel] Does openvpn 2.3.2 has memory leak? (addendum3 and 4) Hi Arno, It is acceptable for me that memory can be used again in new connection. Hi Gert, It is very helpful, thank you so much for your help. Thanks to all of you for developing so excellent and powerful open source project (also complicated for me:) ). Look forward to openvpn 2.3.3. Thanks, Brad Zhang On Fri, Nov 22, 2013 at 6:15 PM, Gert Doering <g...@greenie.muc.de> wrote: Hi, On Fri, Nov 22, 2013 at 10:51:27AM +0100, arno.oderm...@ch.schindler.com wrote: > Dear Gert, Brad all, > > as I also had reported to have recognized, that memory was not freed, even > > though the openvpn disconnect-script was disconnecting all of the 3400 > Openvpn-sessions (pls see mail below). > Would you think, this is also improved by the change from malloc to > calloc, so we could update to 2.3.3 to improve the memory-leak situation? Using malloc() or calloc() will neither affect the total memory used, nor any fragmentation issues or mem leaks. It's just about guaranteeing that allocated memory is zeroed-out. 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 ****************************************************** Notice: The information contained in this message is intended only for use of the individual(s) named above and may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient of this message you are hereby notified that you must not use, disseminate , copy it in any form or take any action in reliance of it. If you have received this message in error please delete it and any copies of it and notify the sender immediately. *******************************************************
