[asterisk-bugs] [JIRA] (ASTERISK-22944) Reload Memory Leak.
Matt Jordan (JIRA)
noreply at issues.asterisk.org
Sat Dec 7 13:55:03 CST 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-22944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=212675#comment-212675 ]
Matt Jordan commented on ASTERISK-22944:
----------------------------------------
I'm going to go ahead and close out this issue as "Not a Bug".
In the future, if you run into something like this, it is important to keep in mind that Asterisk does not have a single configuration repository.
Each module - as well as files within the Asterisk core - are responsible for reading, parsing, and storing the configuration data provided by the Asterisk static conf files. Hundreds of such objects are created during a module load. Without knowing what modules you have loaded, which modules are being reloaded, and how the reload is being issued, you are asking the bug marshals to find a needle in a stack of needles, while telling them only that "there is a single needle that has a problem". :-)
If you continue to have problems with module reloads, at a minimum, please isolate which module is causing the problem and attach the .conf file for the module that reproduces the issue.
> Reload Memory Leak.
> -------------------
>
> Key: ASTERISK-22944
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-22944
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Affects Versions: 11.6.0
> Environment: CentOS release 6.4
> Reporter: Jean-Marc Pigeon
> Assignee: Matt Jordan
>
> System in production, work no trouble, found the used memory was a little bit high
> VSZ 203632, RSS 76152
> Restarted asterisk (service asterisk restart)
> New Memory values are 81636 48376 (rather stable while calls are processed).
> done an asterisk -rx "reload"
> New Memory values are 115128 82524
> new asterisk reload
> New Memory values are 147112 115200
> So it seems each time the SAME configuration is reloaded, used memory increase.
> test done on 2 different asterisks (but same asterisk versions).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list