[asterisk-bugs] [JIRA] (ASTERISK-27532) ERROR[5383][C-00003919] astobj2.c: Excessive refcount 100000 reached on ao2 object 0x142f648

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-27532:
------------------------------------------

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

> ERROR[5383][C-00003919] astobj2.c: Excessive refcount 100000 reached on ao2 object 0x142f648
> --------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27532
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27532
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly.
>    Affects Versions: 13.17.0
>         Environment: Sangoma Freepbx official distro FreePBX 13.0.192.16
> Asterisk 13.17.0
>            Reporter: Mohit Taneja
>            Assignee: Mohit Taneja
>              Labels: fax, webrtc
>         Attachments: console.txt
>
>
> Hi
> We are recently installed Freepbx distro “FreePBX 13.0.192.16” running “Asterisk 13.17.0” on a x86_64 running Linux. From last 2 weeks the CPU suddenly goes to 100% utilization everyday between 9:50 AM EDT to 10:30 AM EDT.
> In the full logs we saw below error during the high CPU utilization. Once the error stop appearing the CPU agin goes to normal
> I have disabled CDR Reports and Call Recording Report modules but the problem is still happening



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