On Nov 15, 2005, at 7:29 PM, Steven Reddie wrote:
David,
If 36 bytes are being dynamically allocated and not being freed how is
it
not a leak?
Steven
Because it only happens once.
Imagine that when you shut off a faucet, water drips out for the next
ten seconds and then stops. That's not a leak, and it's not a problem.
What would be (both a problem and a leak) is water continually
dripping at a regular frequency.
The 36 bytes is not considered a leak because it's acquired only once
as a part of initialization, not proportionally to the use of your
application. And it does get released -- when the process exits. :-)
If it's a problem, maybe you should invest in a RAM upgrade... :-D
Josh
-----Original Message-----
[mailto:[EMAIL PROTECTED] On Behalf Of David Schwartz
Sent: Wednesday, 16 November 2005 10:09 AM
These are 36 bytes that are consumed and used by the library. They
are not leaked but they cannot be freed.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
