[asterisk-bugs] [Asterisk 0014680]: unfreed memory in astobj2.c

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14680 
====================================================================== 
Reported By:                caspy
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14680
Category:                   Core/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0.6 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-16 15:17 CDT
Last Modified:              2009-03-16 23:22 CDT
====================================================================== 
Summary:                    unfreed memory in astobj2.c
Description: 
*CLI> core show uptime
System uptime: 2 days, 11 hours, 3 minutes, 56 seconds
Last reload: 2 days, 11 hours, 3 minutes, 56 seconds

*CLI> core show channels
Channel              Location             State   Application(Data)
0 active channels
0 active calls
44278 calls processed

*CLI> core show locks
[no lock at all]

*CLI> memory show summary astobj2.c
       420 bytes in 35 allocations in function 'ao2_link' of 'astobj2.c'
   5350600 bytes in 22225 allocations in function 'ao2_alloc' of
'astobj2.c'
5351020 bytes allocated in 22260 allocations

# rasterisk -x 'memory show allocations astobj2.c' | sort | uniq -c | sort
-rn
  22165        240 bytes allocated in            ao2_alloc at line   256
of astobj2.c
     44        508 bytes allocated in            ao2_alloc at line   256
of astobj2.c
     35         12 bytes allocated in             ao2_link at line   394
of astobj2.c
      5        548 bytes allocated in            ao2_alloc at line   256
of astobj2.c
      5        472 bytes allocated in            ao2_alloc at line   256
of astobj2.c
      2        676 bytes allocated in            ao2_alloc at line   256
of astobj2.c
      2        484 bytes allocated in            ao2_alloc at line   256
of astobj2.c
      1 5351020 bytes allocated in 22260 allocations
      1        968 bytes allocated in            ao2_alloc at line   256
of astobj2.c
      1        260 bytes allocated in            ao2_alloc at line   256
of astobj2.c


you can see here a 22165 allocations for 240 bytes, that was not released
(other are not so significant, but can be the same trouble).
and their count is constantly growing.

what else can i provide to find out a place of leak?

ps: valgrind is not an options, due to very huge slowdown. i've tried it.
:(
====================================================================== 

---------------------------------------------------------------------- 
 (0101837) tilghman (administrator) - 2009-03-16 23:22
 http://bugs.digium.com/view.php?id=14680#c101837 
---------------------------------------------------------------------- 
Try this patch.  You're going to need to turn on MALLOC_DEBUG to turn on
the full debugging, but it should stop showing astobj2.c as the source of
the leak, and instead show where the real leak is located. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-16 23:22 tilghman       Note Added: 0101837                          
======================================================================