[Home]

Summary:ASTERISK-28073: asterisk memory leak
Reporter:Sergey (mastergt)Labels:
Date Opened:2018-09-25 11:48:33Date Closed:2020-01-14 11:13:58.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:CEL/cel_custom
Versions:13.23.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:OS: gentoo linux x64, core: 4.9.76 Intel(R) Xeon(R) CPU E3-1220 V2 @ 3.10GHz GenuineIntel GNU/Linux, 16 Gb RAM, asterisk, installed in custom dir: /usr/local/asterisk-mainAttachments:
Description:then i try to use scheme:
{noformat}
asterisk --> cel_custom(event flow) --> FIFO (pipe) --> perl parcer(listen fifo) --> db.
{noformat}
i,m detected asterisk memory leak.
my cel_custom.conf:
{noformat}
[mappings]

cel => {"type":${CSV_QUOTE(${eventtype})},"time":${CSV_QUOTE(${eventtime})},"toExten":${CSV_QUOTE(${CHANNEL(exten)})},"channame":${CSV_QUOTE(${CHANNEL(channame)})},"data":${CSV_QUOTE(${CHANNEL(appdata)})},"uniqueid":${CSV_QUOTE(${CHANNEL(uniqueid)})},"linkedid":${CSV_QUOTE(${CHANNEL(linkedid)})},"peer":${CSV_QUOTE(${BRIDGEPEER})}}
{noformat}
in the my directory CEL (/usr/local/asterisk-main/var/log/asterisk/cel-custom/):
"mkfifo cel"  -- (shell command in linux)
after a few hours of work:
top shell command in linux show this:
{noformat}
...
6565 ast       20   0 7000660 4,784g  21860 S   5,3 30,5  84:33.44 asterisk
...
{noformat}
i,m using GRAFANA tool for monitoring free memory:
during about 7 hours asterisk "eat" about 3 GB RAM.
this can continue until OOM killer terminate asterisk process.
Comments:By: Asterisk Team (asteriskteam) 2018-09-25 11:48:34.471-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Joshua C. Colp (jcolp) 2018-09-25 12:10:13.456-0500

Does this happen if you don't use a fifo but just instead go to a normal file? The code doesn't do anything special for named pipes and is unaware of them.
By: Asterisk Team (asteriskteam) 2018-10-10 12:00:01.764-0500

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