[asterisk-bugs] [Asterisk 0013235]: Memory leak in Asterisk 1.4 and Trunk

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13235 
====================================================================== 
Reported By:                falves11
Assigned To:                murf
====================================================================== 
Project:                    Asterisk
Issue ID:                   13235
Category:                   Core/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 13058 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-08-04 18:31 CDT
Last Modified:              2008-08-26 17:51 CDT
====================================================================== 
Summary:                    Memory leak in Asterisk 1.4 and Trunk
Description: 
Both versions of Asterisk have a huge memory leak. I thought that it was
Trunk only and ported my app to 1.4. After 1 day and 17 hours the memory
has gone up 1.2 GB. I only have 300 open calls. My machine is open for
inspection. I am not using "malloc debug" and "don't optimize", for
performance reasons,but I will restart tonight the server. if somebody
wants to suggest any diagnostic technique, please let me know before I
restart.
====================================================================== 

---------------------------------------------------------------------- 
 (0091771) murf (administrator) - 2008-08-26 17:51
 http://bugs.digium.com/view.php?id=13235#c91771 
---------------------------------------------------------------------- 
I believe you, but that does not help me find the problem. You were going
to compile asterisk with DONT_OPTIMIZE, and run it under valgrind for a
while, (cmd: algrind --leak-check=full --show-reachable=yes asterisk -cgv),
 until it processed 10 to 100 calls or so, and then shut down asterisk with
"stop gracefully", and capture all the output, which should tell us in
great detail where the leak is happening.

It could be in the odbc libs, the backend, but we won't know for sure
where or how until you do the above.

If you cannot do the above, we'll have to close the bug until we get more
data. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-26 17:51 murf           Note Added: 0091771                          
======================================================================