[asterisk-bugs] [Asterisk 0014636]: memory leak in "strings.c"

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14636 
====================================================================== 
Reported By:                pj
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   14636
Category:                   Core/PBX
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     confirmed
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 180373 
Request Review:              
====================================================================== 
Date Submitted:             2009-03-10 05:59 CDT
Last Modified:              2009-03-23 11:25 CDT
====================================================================== 
Summary:                    memory leak in "strings.c"
Description: 
memory allocations for strings.c continuously growing, 
after 4 days uptime and small amout of call processed,
my asterisk eats 120MB of RAM.

mmlog is empty

*CLI> core show calls uptime
0 active calls
320 calls processed
System uptime: 4 days, 15 hours, 32 minutes, 58 seconds


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0014680 unfreed memory in try_calling
====================================================================== 

---------------------------------------------------------------------- 
 (0102078) tilghman (administrator) - 2009-03-23 11:25
 http://bugs.digium.com/view.php?id=14636#c102078 
---------------------------------------------------------------------- 
I really don't think there's that much difficulty with the current
statistics.  What I can consider memory leaks are all solved.  This
ballooning of 22MB to 58MB is illusory, I believe, as most of the memory
within that space is actually unallocated.  It was used while you were
processing calls, but memory is never released back to the kernel, once
allocated (until the process ends).  However, the memory is unlikely to
increase beyond that 58MB, unless you throw a larger quantity of calls than
you previously had at the system. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-23 11:25 tilghman       Note Added: 0102078                          
======================================================================