Re: [tpm2] Memory Leak stemming from Esys_Initialize

Re: [tpm2] Memory Leak stemming from Esys_Initialize

[Timothy Le]

[-- Attachment #1: Type: text/plain, Size: 830 bytes --]

Hi,
Thank you for your e-mail. I have the most recent version of TSS, including the changes to the test made yesterday. I still have the same leak (memory allocated in CRYPTO_malloc and also CRYPTO_REALLOC) are not freed.



On 8/19/19, 11:19 AM, "Tadeusz Struk" <tadeusz.struk(a)intel.com> wrote:

    Hi Timothy,
    On 8/16/19 3:33 PM, Timothy Le wrote:
    > It seems that there is memory getting allocated in CRYPO_malloc that Esys_Finalize is not freeing. I have traced the code, but I don’t have access to EVP_add_digest and the other inner function calls. Would someone be able to give me advice on how to free this memory?
    
    Could you specify what version of TSS are you using?
    There was number of fixes merged in recently to fix these leaks.
    
    Thanks,
    -- 
    Tadeusz
    

Re: [tpm2] Memory Leak stemming from Esys_Initialize

[Tadeusz Struk]

[-- Attachment #1: Type: text/plain, Size: 473 bytes --]

Hi Timothy,
On 8/16/19 3:33 PM, Timothy Le wrote:
> It seems that there is memory getting allocated in CRYPO_malloc that Esys_Finalize is not freeing. I have traced the code, but I don’t have access to EVP_add_digest and the other inner function calls. Would someone be able to give me advice on how to free this memory?

Could you specify what version of TSS are you using?
There was number of fixes merged in recently to fix these leaks.

Thanks,
-- 
Tadeusz

[tpm2] Memory Leak stemming from Esys_Initialize

[Timothy Le]

[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]

Hello,

I am working on a program that involves using Esys_Initialize. After calling Esys_Initialize and running the rest of the program, I call Esys_Finalize. However, I have the following output from valgrind:


==14825== 24 bytes in 1 blocks are still reachable in loss record 518 of 545

==14825==    at 0x4C2DB8F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)

==14825==    by 0x5969E77: CRYPTO_malloc (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0)

==14825==    by 0x5A21F85: lh_insert (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0)

==14825==    by 0x596CC54: OBJ_NAME_add (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0)

==14825==    by 0x5A2C565: EVP_add_digest (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0)

==14825==    by 0x5A30F4A: OpenSSL_add_all_digests (in /lib/x86_64-linux-gnu/libcrypto.so.1.0.0)

==14825==    by 0x50CC9FE: iesys_cryptossl_init (esys_crypto_ossl.c:1118)

==14825==    by 0x50BDE5B: iesys_initialize_crypto (esys_crypto.c:537)

==14825==    by 0x50BB474: Esys_Initialize (esys_context.c:81)

It seems that there is memory getting allocated in CRYPO_malloc that Esys_Finalize is not freeing. I have traced the code, but I don’t have access to EVP_add_digest and the other inner function calls. Would someone be able to give me advice on how to free this memory?

Thank you

Timothy

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5101 bytes --]