[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-12 08:35 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0091338) falves11 (reporter) - 2008-08-12 08:35
 http://bugs.digium.com/view.php?id=13235#c91338 
---------------------------------------------------------------------- 
You do actually have the function MINIXEL_ROUTING. It is defined in
func_odbc and it means it is a call to the database. I don't think you can
simulate my application entirely. I will run the valgrind command as soon
as possible. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-12 08:35 falves11       Note Added: 0091338                          
======================================================================