[asterisk-bugs] [JIRA] (ASTERISK-28568) Potential memory leak on core reload

Asterisk Team (JIRA) noreply at issues.asterisk.org
Mon Oct 21 12:00:48 CDT 2019


    [ https://issues.asterisk.org/jira/browse/ASTERISK-28568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=248486#comment-248486 ] 

Asterisk Team commented on ASTERISK-28568:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> Potential memory leak on core reload
> ------------------------------------
>
>                 Key: ASTERISK-28568
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28568
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Configs/Basic-PBX
>    Affects Versions: 16.5.0
>         Environment: CentOS 7 64Bit x86_64
>            Reporter: Michael Maier
>            Assignee: Michael Maier
>            Severity: Minor
>         Attachments: etc_asterisk.tar.gz, memory-consumption-reload.csv
>
>
> Executing "core reload"s seem to consume more and more memory. 
> This is an example done with the attached simple configuration (based on FreePBX 14). Memory usage is measured with
> ps aux | grep sbin/asterisk | grep -v grep
> The memory value in the attached sheet is based on the RSS column of ps.
> Most reloads are done without any change. If there are more trunks / extensions, routes, ... the memory usage is growing much faster.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list