Summary:	ASTERISK-28414: Asterisk crash on internal calls
Reporter:	Martin Nyström (martin.nystrom)	Labels:
Date Opened:	2019-05-14 03:48:47	Date Closed:	2019-05-14 06:37:41
Priority:	Critical	Regression?	No
Status:	Closed/Complete	Components:	Applications/app_queue
Versions:	13.20.0	Frequency of Occurrence	Occasional
Related Issues:
Environment:	CentOS Linux release 7.5.1804 Linux 3.10.0-862.11.6.el7.x86_64 #1 SMP Tue Aug 14 21:49:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux	Attachments:	( 0) call.txt ( 1) Dbz8CRZC.txt
Description:	We have experienced that Asterisk randomly crashes when performing internal calls to other queues. I am not actually sure in this case if it was a transfer or not to the other queue since I never saw any bridging. It could maybe be that the actual transfer caused Asterisk to crash therefor not outing any logs for it. I have collected the GDB info from the core dump and I will attach it to this issue. According to the core dump the following seems to have triggered the crash (Attached file call.txt)
Comments:	By: Asterisk Team (asteriskteam) 2019-05-14 03:48:49.428-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: Martin Nyström (martin.nystrom) 2019-05-14 03:49:13.830-0500 core crash file By: Martin Nyström (martin.nystrom) 2019-05-14 04:10:13.608-0500 Call trigger By: Martin Nyström (martin.nystrom) 2019-05-14 04:38:46.031-0500 It seems that the caller_snapshot is empty (gdb) print queue_data->member_uniqueid $1 = (const ast_string_field) 0x7f5964022a76 "1557818604.80608" (gdb) print caller_snapshot $2 = (struct ast_channel_snapshot *) 0x0 (gdb) By: Martin Nyström (martin.nystrom) 2019-05-14 04:57:57.122-0500 This seems to be fixed in 13.24.0 Change ID I37334ea184ebb56e54471496b82937d4927815a0 No further action is required from my end.