[asterisk-bugs] [Asterisk 0013235]: Memory leak in Asterisk 1.4 and Trunk
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Aug 26 23:56:06 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-08-26 23:56 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.
======================================================================
----------------------------------------------------------------------
(0091779) falves11 (reporter) - 2008-08-26 23:56
http://bugs.digium.com/view.php?id=13235#c91779
----------------------------------------------------------------------
The bug runs across all versions, and I mentioned. I cannot run valgrind
since I have 100% of my business in that box. If I stop the app I lose tons
of money. Right now is 1:00 AM and asterisk has 7 calls and 730 MB.
rhel5-225*CLI> odbc show
Name: routing>
DSN: routing
Pooled: yes
Limit: 1000
Connections in use: 0
Name: global
DSN: mssql
Pooled: yesLI>
Limit: 1000
Connections in use: 6
Connection 1: connected
Connection 2: connected
Connection 3: connected
Connection 4: connected
Connection 5: connected
Connection 6: connected
rhel5-225*CLI> cdr status
CDR logging: enabled
CDR mode: simple
CDR output unanswered calls: no
CDR registered backend: cdr_manager
CDR registered backend: ODBC
Issue History
Date Modified Username Field Change
======================================================================
2008-08-26 23:56 falves11 Note Added: 0091779
======================================================================
More information about the asterisk-bugs
mailing list