[asterisk-bugs] [JIRA] (ASTERISK-27591) Frack errors in stasis.c and memory leakage
Kevin Harwell (JIRA)
noreply at issues.asterisk.org
Wed Jan 17 10:14:49 CST 2018
[ https://issues.asterisk.org/jira/browse/ASTERISK-27591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241622#comment-241622 ]
Kevin Harwell commented on ASTERISK-27591:
------------------------------------------
Please attach the dialplan used in the scenario and any other relevant conf files (sip.conf or pjsip.conf, manager.conf, etc...). Also as it sounds like by running the same scenario over again causes the issue can you post a debug log of at least one run of the scenario. More info on how to collect debug information can be found [here|https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information].
Thanks!
> Frack errors in stasis.c and memory leakage
> -------------------------------------------
>
> Key: ASTERISK-27591
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-27591
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/Stasis
> Affects Versions: 14.3.0, 15.1.2, 15.1.4
> Environment: RHEL 7.4, Centos 7.3
> Reporter: Siruja Maharjan
> Attachments: backtrace_stasis.log, messages_frack.txt
>
>
> The call scenario is as below.
> A calls B. Then via AMI asterisk sends a missed call to B.
> It was observed that memory usage by asterisk process was in increasing mode. Additionally after around 100000 calls following message is logged in messages file.
> {quote}
> [Jan 9 18:06:39] ERROR[68501] stasis.c: Excessive refcount 100000 reached on ao2 object 0x1b5fb00
> [Jan 9 18:06:39] ERROR[68501] stasis.c: FRACK!, Failed assertion Excessive refcount 100000 reached on ao2 object 0x1b5fb00 (0)
> {quote}
> The error is observed after around 100000 calls after each restart.
> Backtrace is attached.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list