| Summary: | ASTERISK-29331: publish_msg: FRACK!, Failed assertion bad magic number | ||||
| Reporter: | Lucas Souza (lucasvs) | Labels: | |||
| Date Opened: | 2021-03-08 09:55:54.000-0600 | Date Closed: | 2021-03-08 10:26:07.000-0600 | ||
| Priority: | Minor | Regression? | |||
| Status: | Closed/Complete | Components: | Resources/res_ari Resources/res_stasis | ||
| Versions: | 18.2.1 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | Attachments: | ( 0) ast-dump-files.zip | |||
| Description: |
After updating to version 18.2.1 (from 17.9.0) the asterisk is crashing with the following backtrace: {code} [Mar 6 08:52:52] ERROR[33963]: stasis.c:1478 publish_msg: FRACK!, Failed assertion bad magic number 0x7f5 for object 0x7f509000e710 (0) [Mar 6 08:52:52] ERROR[33963]: Got 18 backtrace records # 0: asterisk __ast_assert_failed() # 1: asterisk <unknown>() # 2: asterisk __ao2_lock() # 3: asterisk <unknown>() # 4: asterisk stasis_publish() # 5: asterisk bridge_topics_destroy() # 6: asterisk <unknown>() # 7: asterisk __ao2_ref() # 8: asterisk <unknown>() # 9: asterisk __ao2_ref() #10: asterisk ast_bridge_depart() #11: [0x7f515539e7af] res_stasis.so res_stasis.c:1596 stasis_app_exec() #12: [0x7f5154c07310] app_stasis.so app_stasis.c:105 app_exec() #13: asterisk pbx_exec() #14: [0x7f5155380123] res_stasis_snoop.so res_stasis_snoop.c:275 snoop_stasis_thread() #15: asterisk <unknown>() #16: [0x7f5159dedea7] libpthread.so.0 pthread_create.c:478 start_thread() #17: [0x7f5159a18def] libc.so.6 clone.S:97 __GI___clone() {code} | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2021-03-08 09:55:55.716-0600 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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Benjamin Keith Ford (bford) 2021-03-08 10:16:51.576-0600 Do you have a way to reproduce the crash, or do you have a description of what operations Asterisk is performing when the crash occurs? That would help narrow down the issue. Also, 17 to latest 18 is a big jump. Have you tried older versions of 18 to see if this is a problem with 18 in general, or just the newest release? By: Joshua C. Colp (jcolp) 2021-03-08 10:26:07.371-0600 This is actually a duplicate of ASTERISK-29187. | ||||