This appears to be a usage problem where the library is not being de-inited
properly. This should be resolved anyway in 1.1.0 with auto-deinit.
Closing ticket.
Matt
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=2363
Please log in as guest with password guest if prompted
--
Roumen, you're right. Does the leak go away when the cleanup_all_ex_data is
called?
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=2363
Please log in as guest with password guest if prompted
--
openssl-dev mailing list
To unsubscribe:
Roumen, you're right. Does the leak go away when the cleanup_all_ex_data is
called?
--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
It is expected DH_free(DH_new()); to leaks memory. Usually XXX method
initialize "extra data".
Sample code is without code that clear library, at least
CRYPTO_cleanup_all_ex_data is missing.
Roumen
--
Ticket here: http://rt.openssl.org/Ticket/Display.html?id=2363
Please log in as guest
from Jan:
I'm not exactly saying that "DH_free(DH_new()) leaks memory when in a DLL on
Solaris", what I'm saying is that libcrypto does not free memory that it should
in "#pragma fini(xxx)". I assume there is some memory allocated first time
DH_new() is used and that memory is never freed on
