I have also noticed a leak under Windows/32 using 9.6a. I have started the task of locating the source of the leak. My memory "tester" says it is OpenSSL. I have done everything I can to insure that everything is closed and freed. The best I can get is down to a 4K leak.
I'm not convicned it is OpenSSl, although it appears to be. There is a function in openssl that will help with leak detection. I shouldn't have to do this though. If I close the sockets (and make ure they are closed) and close and free all OPenSSL contexts, the memory should be freed. I'm not complaining, just thought I would let you know I am having some of the same problems. Scott -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Per Jakobsson (QTX) Sent: Monday, February 04, 2002 4:52 AM To: '[EMAIL PROTECTED]' Cc: Tobias Austrell (ETX); Roger Jonsson K (QTX) Subject: Memory leak Hi. First time using this, we'll see if the question is "old". Anyway, we are using open ssl in a project at Ericsson. In an application there is a socket layer encapculating the ssl functionallity. Using these sockets works fine. Unfortunately, I have discovered a memory leak when using these sockets. If a socket is opened, used and closed, there is 9040 bytes left on the heap. If I open a socket, but close it before sll handshake is finnished, there is no leakage. My question is, could this be an error the open sll version we are using, or are we using OpenSsl in an incorrect way? Any ideas? OS: OSE Delta. Our version: 0.9.5a ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED] ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]