| Summary: | ASTERISK-28380: Asterisk CLI Showing ERRORS: frame.c: Excessive refcount 100000 reached on ao2 object when total calls reached almost 30000 count. | ||
| Reporter: | Talha Omair (TalhaOmair) | Labels: | |
| Date Opened: | 2019-04-10 10:57:06 | Date Closed: | 2019-04-10 12:07:59 |
| Priority: | Major | Regression? | Yes |
| Status: | Closed/Complete | Components: | . I did not set the category correctly. |
| Versions: | 14.4.1 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Ubuntu 16.04 Kernel 4.4.0-96-generic x86_64 CPU(s) 4 Model Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz | Attachments: | |
| Description: | Asterisk installed from source following this link https://wiki.asterisk.org/wiki/display/AST/Installing+Asterisk+From+Source.
We are dialing outbound and received inbound calls. Also using .net stasis application for outbound and inbound calls. When start dialing in the morning everything goes fine. As soon as, total call reached 30000 in the evening asterisk CLI starts showing following ERRORS in bulk. ERROR[22968] frame.c: Excessive refcount 100000 reached on ao2 object 0x3546a00. ERROR[22968] frame.c: FRACK!, Failed assertion Excessive refcount 100000 reached on ao2 object 0x3546a00. ERROR[16040] bridge_softmix.c: Excessive refcount 100000 reached on ao2 object 0x3546a00. ERROR[16040] bridge_softmix.c: FRACK!, Failed assertion Excessive refcount 100000 reached on ao2 object 0x3546a00 (0). This figure of 30k is represents total calls not concurrent. Although, currently no asterisk crash but it's worrisome. Please help me resolve these errors. Also let me know if need anything else from my end. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2019-04-10 10:57:07.313-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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: Malcolm Davenport (mdavenport) 2019-04-10 12:07:43.666-0500 Per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions | ||