Skip to content

GitLab

jami-project
jami-project
Closed
Opened by RingBot@RingBotOwner

Daemon: memory leak during call

Issue generated from Tuleap's migration script. Originally submitted by: Guillaume Roguez (guillaume)

Using ASAN (address sanitizer) I discovered that I got a memory leak report on non-free av\_malloc, only when I do a call (video was enabled on both peer)

This is the ASAN report related to libav functions:

  
Direct leak of 51568 byte(s) in 63 object(s) allocated from:  
    \#0 0x7ffff70f4456 in posix\_memalign (/lib64/libasan.so.2+0x99456)  
    \#1 0x37a381c86f in av\_malloc (/lib64/libavutil.so.54+0x37a381c86f)  
  
Indirect leak of 42080 byte(s) in 100 object(s) allocated from:  
    \#0 0x7ffff70f4456 in posix\_memalign (/lib64/libasan.so.2+0x99456)  
    \#1 0x37a381c86f in av\_malloc (/lib64/libavutil.so.54+0x37a381c86f)  
  
Indirect leak of 2041 byte(s) in 250 object(s) allocated from:  
    \#0 0x7ffff70f3d8a in realloc (/lib64/libasan.so.2+0x98d8a)  
    \#1 0x37a381cab0 in av\_strdup (/lib64/libavutil.so.54+0x37a381cab0)  
  
Indirect leak of 1840 byte(s) in 43 object(s) allocated from:  
    \#0 0x7ffff70f3d8a in realloc (/lib64/libasan.so.2+0x98d8a)  
    \#1 0x37a38137ac in av\_dict\_set (/lib64/libavutil.so.54+0x37a38137ac)  
  
Indirect leak of 160 byte(s) in 20 object(s) allocated from:  
    \#0 0x7ffff70f3d8a in realloc (/lib64/libasan.so.2+0x98d8a)  
    \#1 0x3c4bb22f08 in avformat\_new\_stream (/lib64/libavformat.so.56+0x3c4bb22f08)