INTERPRETING THE HEAP TRACE

phanikarthik
Posts: 4
Joined: Wed Oct 04, 2017 3:53 am

INTERPRETING THE HEAP TRACE

Postby phanikarthik » Thu Jan 25, 2018 12:56 pm

Hello all,

I have enabled the heap tracing and the report i get ends like...

Code: Select all

#1 804 bytes 'leaked' in trace (19 allocations)
#2 total allocations 25640 total frees 25740
#3 MALLOC_CAP_8BIT potential leak: Before 200368 bytes free, After 199488 bytes free (delta 880)
#4 MALLOC_CAP_32BIT potential leak: Before 259412 bytes free, After 258532 bytes free (delta 880)
#2 states that frees are more than allocs. this is not possible right? then why the report is suggesting that?

In addition to the heap trace report I also get lines 3 and 4(even if test case is run with heap tracing disabled.)
So, which leaks should I look to fix ?...804 bytes shown in line #1 or a totally different figure suggested in line-3 and line-4.


Thanks
Phani Karthik

Who is online

Users browsing this forum: Dennie and 100 guests