[asterisk-bugs] [Asterisk 0016538]: memory leak in confic.c
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Jan 4 13:35:44 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16538
======================================================================
Reported By: sdaniels
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16538
Category: Core/Configuration
Reproducibility: always
Severity: crash
Priority: normal
Status: feedback
Asterisk Version: Older 1.4 - please test a newer version
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-01-04 03:40 CST
Last Modified: 2010-01-04 13:35 CST
======================================================================
Summary: memory leak in confic.c
Description:
Asterisk is using more and more memory (up to 2GB), even when no calls are
placed.
Versions: 1.4.19.2 -1.4.22
1.4.28 not usable in my case.
After a few days Asterisk is using so much memory, that only a restart
make it usable again, because it is getting dead slow and all RTP data,
that passes asterisk is choppy.
After a restart astersik uses around 11MB. As soon as the first phones
reregisters, memory usage is increasing. Reboot of all phones makes it even
faster.
Memory is allocated by config.c in ast_variable_new at line 194
memory show allocations
45 bytes allocated in ast_variable_new at line 194 of config.c
After a few hours I had 358194 of the above.
Running asterisk like that:
valgrind --leak-check=full --show-reachable=yes asterisk -cgv
used over 200MB of memory after around 4h and all together 4 calls!
stop gracefully did not work any more.
======================================================================
----------------------------------------------------------------------
(0115982) pkempgen (reporter) - 2010-01-04 13:35
https://issues.asterisk.org/view.php?id=16538#c115982
----------------------------------------------------------------------
> pkempgen: Am I understanding you correctly, then, that there are
> no open issues that would prevent the reporter from upgrading to
> the latest 1.4?
Frankly I don't know. I have more or less quit evaluating new
releases of Asterisk 1.4 more than a year ago because they did not
work for us for quite some time. Instead we're preparing for the
switch to Asterisk 1.6.x or 1.8 but that means more work than just
a matter of days.
In respect of Gemeinschaft I recommend against an upgrade to the
latest 1.4 because all kinds of nasty side effects might occur.
Don't know if the BLF problems are still present in the latest 1.4.
IMHO the reporter has a "legitimate interest" not to upgrade.
However I realize that this issue could be in a catch-22 situation
then. No idea how to move this forward.
Issue History
Date Modified Username Field Change
======================================================================
2010-01-04 13:35 pkempgen Note Added: 0115982
======================================================================
More information about the asterisk-bugs
mailing list