[asterisk-bugs] [Asterisk 0013452]: skinny memory leak

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13452 
====================================================================== 
Reported By:                pj
Assigned To:                qwell
====================================================================== 
Project:                    Asterisk
Issue ID:                   13452
Category:                   Channels/chan_skinny
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 141949 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-09-10 04:31 CDT
Last Modified:              2008-09-13 18:41 CDT
====================================================================== 
Summary:                    skinny memory leak
Description: 
memory allocations continuously growing,
asterisk has only two idle 7920 phones during monitoring period,
no skinny calls during this time window (about 15hours), 
perhaps some leak in keepalives handling?

  176148 bytes in 3284 allocations in file 'chan_skinny.c'
  307800 bytes in 7523 allocations in file 'chan_skinny.c'






======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013294 crash after "Hard hangup called wh...
====================================================================== 

---------------------------------------------------------------------- 
 (0092471) wedhorn (reporter) - 2008-09-13 18:41
 http://bugs.digium.com/view.php?id=13452#c92471 
---------------------------------------------------------------------- 
new patch (memleak4.diff). I was a bit overzealous with freeing the subs
which appears to have caused some issues. Only a single ast_free(sub).

Unfortunately it's difficult to force a crash (only managed 1 - mvanbaak
got 1 as well with memleak3.diff) so not certain that this actually fixes
the issue.

pj, as it seems to be easiest for you to get crashes, can you please test.
Not certain that memleak3 is related to your earlier crashes. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-13 18:41 wedhorn        Note Added: 0092471                          
======================================================================