[Home]

Summary:ASTERISK-27054: Crash In Queueing Frame
Reporter:Joshua Elson (joshelson)Labels:
Date Opened:2017-06-13 11:41:21Date Closed:2020-01-14 11:14:15.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:
Versions:14.5.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) crash-on-queue-frame.txt
Description:Just started seeing a new crash on Asterisk 14.5 on an outbound call that is answered very quickly (using the Polycom auto-answer header).

Still looking for more repro scenarios, but figured I'd post in case anyone else has seen this.
Comments:By: Asterisk Team (asteriskteam) 2017-06-13 11:41:22.382-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: Joshua Elson (joshelson) 2017-06-13 11:43:31.497-0500

Backtrace attached. This happens on pjsip endpoints.

By: George Joseph (gjoseph) 2017-06-14 09:22:23.712-0500

I looked at the backtrace but the lines that tell what the crash actually was are missing.   It just shows a thread trying to calloc 1 302 byte structure.  It doesn't say that was what caused the crash.

Can you post the full "thread apply all bt full"?
You can use /var/lib/asterisk/scripts/ast_coredumper and attach the tarball it can create.




By: Asterisk Team (asteriskteam) 2017-06-28 12:00:01.977-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