[Home]

Summary:ASTERISK-28464: FRACK!, Failed assertion with res_pjsip
Reporter:Kirsty Tyerman (ktyerman)Labels:pjsip
Date Opened:2019-06-27 18:43:35Date Closed:2019-07-12 12:00:02
Priority:MajorRegression?
Status:Closed/CompleteComponents:Resources/res_pjsip
Versions:16.1.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:When I leave asterisk running, after some amount of time I find the following excessive refcount issue. It doesnt seem to crash asterisk, but I'm also unsure what is causing this issue.

{noformat}
[Jun 27 08:56:04] ERROR[27585]: res_sorcery_config.c:186 sorcery_config_retrieve_id: Excessive refcount 100000 reached on ao2 object 0x55f5ec2f98d0
[Jun 27 08:56:04] ERROR[27585]: res_sorcery_config.c:186 sorcery_config_retrieve_id: FRACK!, Failed assertion Excessive refcount 100000 reached on ao2 object 0x55f5ec2f98d0 (0)
Got 20 backtrace records
#0: [0x55f5e99aca8d] /usr/sbin/asterisk(__ao2_ref+0x29d) [0x55f5e99aca8d]
#1: [0x55f5e99ae6a6] /usr/sbin/asterisk(+0x6d6a6) [0x55f5e99ae6a6]
#2: [0x55f5e99ae950] /usr/sbin/asterisk(__ao2_find+0x30) [0x55f5e99ae950]
#3: [0x7f223068d050] /usr/lib64/asterisk/modules/res_sorcery_config.so(+0x3050) [0x7f223068d050]
#4: [0x55f5e9aa9a42] /usr/sbin/asterisk(ast_sorcery_retrieve_by_id+0xc2) [0x55f5e9aa9a42]
#5: [0x7f223005c0c9] /usr/lib64/asterisk/modules/res_pjsip.so(+0x270c9) [0x7f223005c0c9]
#6: [0x7f2230063e54] /usr/lib64/asterisk/modules/res_pjsip.so(+0x2ee54) [0x7f2230063e54]
#7: [0x7f22300673ce] /usr/lib64/asterisk/modules/res_pjsip.so(+0x323ce) [0x7f22300673ce]
#8: [0x55f5e99ae355] /usr/sbin/asterisk(+0x6d355) [0x55f5e99ae355]
#9: [0x55f5e99ae8e0] /usr/sbin/asterisk(__ao2_callback+0x20) [0x55f5e99ae8e0]
#10: [0x7f2230070d2b] /usr/lib64/asterisk/modules/res_pjsip.so(ast_sip_cli_traverse_objects+0x55b) [0x7f2230070d2b]
#11: [0x55f5e9a0435a] /usr/sbin/asterisk(ast_cli_command_full+0x24a) [0x55f5e9a0435a]
#12: [0x55f5e9a0464c] /usr/sbin/asterisk(ast_cli_command_multiple_full+0x8c) [0x55f5e9a0464c]
#13: [0x55f5e99a84a0] /usr/sbin/asterisk(+0x674a0) [0x55f5e99a84a0]
#14: [0x55f5e9ad49e0] /usr/sbin/asterisk(+0x1939e0) [0x55f5e9ad49e0]
{noformat}
Comments:By: Asterisk Team (asteriskteam) 2019-06-27 18:43:36.746-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: Joshua C. Colp (jcolp) 2019-06-28 04:13:26.772-0500

It appears the bug you have submitted is against a rather old version of a supported branch of Asterisk. There have been many issues fixed between the version you are using and the current version of your branch. Please test with the latest version in your Asterisk branch and report whether the issue persists.

Please see the Asterisk Versions [1] wiki page for info on which versions of Asterisk are supported.
[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions


By: Asterisk Team (asteriskteam) 2019-07-12 12:00:01.874-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