Hi Pekka,
>> More than probably, it's my fault, but I am getting tons of memory leaks
>> in my NTA-based application (using sofia-sip v1.12.8). The worst one is
>> reported by valgrind like this:
>>
>> ==31415== 8,795,284 (1,302,928 direct, 7,492,356 indirect) bytes in
>> 2,692 blocks are definite
Hi again,
Just found that calling nta_incoming_destroy() after having called
nta_incoming_treply() doesn't seem to be the way to proceed. If I remove
the nta_incoming_destroy, valgrind doesn't report any memory leak.
But, I am really worried about how the memory is managed. Even if
valgrind does
Hi all,
More than probably, it's my fault, but I am getting tons of memory leaks
in my NTA-based application (using sofia-sip v1.12.8). The worst one is
reported by valgrind like this:
==31415== 8,795,284 (1,302,928 direct, 7,492,356 indirect) bytes in
2,692 blocks are definitely lost in loss rec
