Hai All, We are running Dtls Calls and we are seeing the following Memory leaks.
1,340 bytes in 5 blocks are still reachable in loss record 2,684 of 3,019 ==22625== at 0x4C28BED: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==22625== by 0x5156347: CRYPTO_malloc (in /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==22625== by 0x51B8AE1: BUF_MEM_grow (in /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==22625== by 0x51F9E68: X509_NAME_oneline (in /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==22625== by 0x51DEF6D: x509_cb (in /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==22625== by 0x51E5C83: ASN1_item_ex_d2i (in /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==22625== by 0x51E62E6: ASN1_item_d2i (in /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0) ==22625== by 0x4E4F0BF: ssl3_get_client_certificate (in /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0) ==22625== by 0x4E67D63: dtls1_accept (in /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0) ==22625== by 0x4E6C384: dtls1_read_bytes (in /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0) ==22625== by 0x4E57626: ssl3_read (in /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0) There are many leaks because of crypto_malloc, just i pasted one for sample purpose. My question is how to free that above allocated memory. Do SSL_free() will clear above memory. Could any help me in this regard. Regards Satya
_______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
