Summary:	ASTERISK-28404: astobj2.c: FRACK, memory leakage
Reporter:	Dmitriy Makarov (atsman)	Labels:
Date Opened:	2019-05-06 03:51:13	Date Closed:	2019-05-27 22:03:21
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	. I did not set the category correctly.
Versions:	13.22.0	Frequency of Occurrence	Occasional
Related Issues:
Environment:	Sangoma Linux release 7.5.1805, VM on Hyper-V	Attachments:
Description:	memory leakage with error messages: [2019-05-06 08:48:18] ERROR[159002][C-0000015f] astobj2.c: Excessive refcount 100000 reached on ao2 object 0x3302740 [2019-05-06 08:48:18] ERROR[159002][C-0000015f] astobj2.c: FRACK!, Failed assertion Excessive refcount 100000 reached on ao2 object 0x3302740 (0) [2019-05-06 08:48:20] ERROR[159040][C-0000015b] astobj2.c: Excessive refcount 100000 reached on ao2 object 0x3301020 [2019-05-06 08:48:20] ERROR[159040][C-0000015b] astobj2.c: FRACK!, Failed assertion Excessive refcount 100000 reached on ao2 object 0x3301020 (0) [2019-05-06 08:49:25] ERROR[160349][C-00000153] astobj2.c: Excessive refcount 100000 reached on ao2 object 0x32cf9b0 [2019-05-06 08:49:25] ERROR[160349][C-00000153] astobj2.c: FRACK!, Failed assertion Excessive refcount 100000 reached on ao2 object 0x32cf9b0 (0)
Comments:	By: Asterisk Team (asteriskteam) 2019-05-06 03:51:15.026-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: George Joseph (gjoseph) 2019-05-08 08:02:28.325-0500 Can you tell me how often this happens? We did some work in this area since 13.22.  Can you upgrade to the latest 13 and see if you still get the FRACKs? By: Dmitriy Makarov (atsman) 2019-05-13 01:39:13.970-0500 this happens when the number of incoming calls exceeds 20, and there are more than 10 in the queue. upgrade standard methods fail. find out how to do it By: George Joseph (gjoseph) 2019-05-13 11:36:40.580-0500 Once you've upgraded I believe those FRACKs will go away. By: Asterisk Team (asteriskteam) 2019-05-27 12:00:01.684-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 By: Dmitriy Makarov (atsman) 2019-05-27 22:02:06.001-0500 after change version to 15.5.0 problem was not repeat By: Asterisk Team (asteriskteam) 2019-05-27 22:02:06.536-0500 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.