[asterisk-bugs] [Asterisk 0014636]: memory leak in "strings.c"
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Apr 3 15:47:02 CDT 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=14636
======================================================================
Reported By: pj
Assigned To: tilghman
======================================================================
Project: Asterisk
Issue ID: 14636
Category: Core/PBX
Reproducibility: always
Severity: minor
Priority: normal
Status: confirmed
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 180373
Request Review:
======================================================================
Date Submitted: 2009-03-10 05:59 CDT
Last Modified: 2009-04-03 15:47 CDT
======================================================================
Summary: memory leak in "strings.c"
Description:
memory allocations for strings.c continuously growing,
after 4 days uptime and small amout of call processed,
my asterisk eats 120MB of RAM.
mmlog is empty
*CLI> core show calls uptime
0 active calls
320 calls processed
System uptime: 4 days, 15 hours, 32 minutes, 58 seconds
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0014680 unfreed memory in try_calling
======================================================================
----------------------------------------------------------------------
(0102707) tilghman (administrator) - 2009-04-03 15:47
http://bugs.digium.com/view.php?id=14636#c102707
----------------------------------------------------------------------
At this point, I'm stumped. Every memory access by the Asterisk code,
other than that by the debugger itself, should be going through the
MALLOC_DEBUG routines. That it isn't suggests one of several
possibilities:
1) The MALLOC_DEBUG routines are leaking (unlikely).
2) You have additional modules that were not compiled with MALLOC_DEBUG
(for example, the addons) that are leaking.
3) One or more of the runtime libraries is itself leaking memory.
You can test the first one by shutting off MALLOC_DEBUG and see if it
still leaks memory. If it still does, then MALLOC_DEBUG is not the
culprit. I'm not sure what else we can do, though.
Issue History
Date Modified Username Field Change
======================================================================
2009-04-03 15:47 tilghman Note Added: 0102707
======================================================================
More information about the asterisk-bugs
mailing list