[asterisk-bugs] [Asterisk 0019065]: Memory leak in utils.c

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19065 
====================================================================== 
Reported By:                cbbs70a
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19065
Category:                   General
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.2.3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-04-04 11:35 CDT
Last Modified:              2011-04-05 09:23 CDT
====================================================================== 
Summary:                    Memory leak in utils.c
Description: 
Running a standard install of Asterisk 1.8.2.3, memory leak grows
unbounded, with Asterisk using up 3GB of memory. The load average
consistently stayed in the range of about 40, when it normally is less than
2. I saw this error:

[Apr  4 11:18:08] ERROR[23602]:
/usr/src/asterisk-1.8.2.3/include/asterisk/utils.h:477 _ast_calloc: Memory
Allocation Failure in function __ast_calloc_with_stringfields at line 1791
of utils.c
====================================================================== 

---------------------------------------------------------------------- 
 (0133372) davidw (reporter) - 2011-04-05 09:23
 https://issues.asterisk.org/view.php?id=19065#c133372 
---------------------------------------------------------------------- 
utils.c tells one very little, because that's simply where memory is
allocated!

What do you mean by a standard build?  What gets installed depends on what
else was installed at the time ./configure was run, even if you don't
customise.  

For a start, you will need to build from source with no optimisation, and
obtain back traces of all running threads.

You may well need to run it under valgrind. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-04-05 09:23 davidw         Note Added: 0133372                          
======================================================================