Another leak: tls_new_client_session

[Sam Hartman]

>>>>> "Alan" == Alan DeKok <aland at deployingradius.com> writes:

    Alan> On Mar 5, 2015, at 12:32 PM, Stefan Paetow <Stefan.Paetow at jisc.ac.uk> wrote:
    >> I've uploaded another two... both with --trace-children=yes, and
    >> one with -v also. Part of the summary in the latter was
    >> interesting in that it referred to 210K in 295 blocks indirectly
    >> lost.

    Alan>   What I find a little odd is that there’s so much memory
    Alan> lost.  The server tries hard to clean up all memory on exit.

    Alan>   It looks like there are definite losses in the trust router
    Alan> code.  There are “open” connection calls, but not “close”
    Alan> connection.  I’m not really worried about that.
Noticed that and am working on those.


    Alan>   But it’s odd that nothing’s being cleaned up on exit.  That
    Alan> makes it much harder to track down real errors.

What I found is that if I let it run for 50,000 requests or so, looking
at the highest usage possibly lost and definitely losts blocks tended to
show the current problem.