[Home]

Summary:ASTERISK-26149: format: Crash when calling from queue
Reporter:Denis S.Davydov (denis.davydov)Labels:
Date Opened:2016-06-25 11:48:24Date Closed:2020-01-14 11:13:29.000-0600
Priority:MinorRegression?
Status:Closed/CompleteComponents:Applications/app_queue Channels/chan_sip/General Core/General
Versions:13.9.1 Frequency of
Occurrence
One Time
Related
Issues:
is duplicated byASTERISK-26152 Crash issue in ast_format_get_type of format.c
Environment:Virtual Machine on ESXi6 (VM Version 11, 4vCPU, 16Gb RAM), OS: CentOS release 6.8 (Final) x86_84Attachments:( 0) backtrace.txt
( 1) backtrace2.txt
( 2) backtrace3.txt
( 3) full.txt
( 4) full2.txt
( 5) scrn1.PNG
( 6) scrn2.PNG
Description:Program terminated with signal 11, Segmentation fault. in ast_format_cap_append_from_cap at format_cap.c:308

backtrace.txt and full.txt are in attachment (bzgrep -B6000 -A30 'by root' /var/log/asterisk/full-20160625-1466845261.bz2 > full.txt)

I can give you configuration snippet by your request. Compiled flags on my Asterisk-PBX is DONT_OPTIMIZE, COMPILE_DOUBLE, LOADABLE_MODULES, BETTER_BACKTRACES, MALLOC_DEBUG, BULD_NATIVE. Btw, I have mmlog, but there is nothing:

{code}
# cat /var/log/asterisk/mmlog
1466784119 - New session
1466801869 - New session
1466842119 - New session
1466846771 - New session
1466847519 - New session
{code}

Comments:By: Asterisk Team (asteriskteam) 2016-06-25 11:48:24.593-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].

By: Denis S.Davydov (denis.davydov) 2016-06-25 11:49:04.777-0500

See attachments.

By: Denis S.Davydov (denis.davydov) 2016-06-25 11:56:35.087-0500

Screenshots of performance of VM in attachments.

By: Denis S.Davydov (denis.davydov) 2016-06-26 00:01:57.965-0500

See attachment with the same two crashed caused by format_cap.c.

backtrace2.txt for core.pbx.autoconnex.ru-2016-06-25T09:26:06+0000
backtrace3.txt for core.pbx.autoconnex.ru-2016-06-25T09:38:34+0000
full2.txt log for above two core dumps (bzgrep -B6000 -A30 'by root' /var/log/asterisk/full-20160625-1466852461.bz2 > full2.txt)

By: Joshua C. Colp (jcolp) 2016-07-14 05:11:09.377-0500

I think we're also going to need the queues.conf, sip.conf, and extensions.conf which would cause this to happen as well.

By: Asterisk Team (asteriskteam) 2016-07-28 12:00:01.284-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