Hi, On Mon, Oct 21, 2013 at 10:34:27AM +0200, arno.oderm...@ch.schindler.com wrote: > thank you for replying. > Do you see any time window, you potentially could have time for this?
I just gave it an initial try (using the "master" branch but that code
should have the same issues, if any, as no (known) fixes have been commited).
Valgrind isn't telling me about any clear mem-leaks yet...
==1953== HEAP SUMMARY:
==1953== in use at exit: 2,560 bytes in 52 blocks
==1953== total heap usage: 52,139 allocs, 52,087 frees, 15,723,723 bytes
allocated
... but I could see memory go up in "while sleep 1; do ps wwup 1953 ; done"
listings at exactly the point in time where renegotiation was taking place,
with two clients connected to it.
I could use some ideas on how to debug this further - if valgrind isn't
complaining, normally our memory management should be OK, but why is
VSZ/RSZ still growing, then...?
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
pgpQBD4qBSvWM.pgp
Description: PGP signature
