[asterisk-bugs] [JIRA] (ASTERISK-27591) Frack errors in stasis.c and memory leakage

[Corey Farrell (JIRA)]

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

Corey Farrell commented on ASTERISK-27591:
------------------------------------------

It looks like none of the recent work I've done on stasis (core or res_stasis) has made it to a release yet.  Unfortunately the refs.txt only shows a minor leak from ODBC.  The line numbers in the latest FRACK matches 15.1.x but are slightly off from 15.2.0.

> 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
>            Assignee: Corey Farrell
>              Labels: pjsip
>         Attachments: backtrace_stasis.log, debug_log, extensions.conf, frack_jan22.txt, manager.conf, messages_frack.txt, messages_log.txt, pjsip.conf, refs.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)