You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your ses
8000
sion.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The memory leak is due to not free'ing the buffer used to write frames. The problem is, at least in the example provided with source, is that 5 memory allocation was declared but only 4 free was called !
Either free the buffer after calling the gwavi_add_frame function or add free(buffer) inside that function befor return'ing. That should stop memory leaks.
Hi and thanks for reporting this. I will try to have a look once but as
5D3F
I do not use this library anymore I don't have a very high incentive to do it. I'll be happy to review a PR though :)
Activity
mtiraouiDH commentedon Sep 10, 2019
The memory leak is due to not free'ing the buffer used to write frames. The problem is, at least in the example provided with source, is that 5 memory allocation was declared but only 4 free was called !
Either free the buffer after calling the gwavi_add_frame function or add free(buffer) inside that function befor return'ing. That should stop memory leaks.
rolinh commentedon Sep 18, 2019
Hi and thanks for reporting this. I will try to have a look once but as 5D3F I do not use this library anymore I don't have a very high incentive to do it. I'll be happy to review a PR though :)
rolinh commentedon Jun 24, 2020
@flok99 Your PR does not decouple features/fixes. I probably want to merge your memory leak fix but not what is related to debian packaging.