[asterisk-bugs] [Asterisk 0013235]: Memory leak in Asterisk 1.4 and Trunk
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Sep 2 18:51:45 CDT 2008
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-09-02 18: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.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0013409 [patch] Huge memory leak because memory...
======================================================================
----------------------------------------------------------------------
(0092000) murf (administrator) - 2008-09-02 18:51
http://bugs.digium.com/view.php?id=13235#c92000
----------------------------------------------------------------------
falves11--
I've already applied the patch to 1.4, trunk, and 1.6.1.
I've written letters to a few folks to let them know the exact revisions
they need to apply (there are 3 now). I suspect they'll let you know
tomorrow, what the schedule will be. But it does look good that this is the
problem that is biting you. Sorry it took so long. My trust in valgrind was
definitely misplaced in this instance.
Issue History
Date Modified Username Field Change
======================================================================
2008-09-02 18:51 murf Note Added: 0092000
======================================================================
More information about the asterisk-bugs
mailing list