> I'm just curious, what was the offending library? I have seen similar memory > issues \ > in the past that I never had a chance to get to the bottom of, actually > openssl \ > behaved differently between 0.9.8i and 0.9.8j. But I'm wondering what > library you \ > had to work around.
It was a library that was created here. Stuff I've written. To be blunt, the bug was in my code. A heretofore little-used data structure wasn't completely being cleaned up. Though each use involved just a pittance of leaked memory, over many thousands of ssl connections in a single process (which is also something new for us) it added up to a lot. Once I fixed my bug, everything was fine. What's interesting is the misleading implication that--based on the fact that whenever the process size increased, it was always in SSL_connect()-- the problem was in openssl. It was not. It turns out that process size increased in openssl only because of problems elsewhere. Had memory not been leaking elsewhere, openssl would have been reusing previously freed memory, maintaining a constant process size. In retrospect, I should have realized that openssl has been so widely used for so long that it is bound to be pretty solid by now. -Mike ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
