[Home]

Summary:ASTERISK-27330: Asterisk crashes sometimes on destruction of RTCP message payload
Reporter:vipul jain (vipuljain)Labels:
Date Opened:2017-10-11 01:46:59Date Closed:2020-01-14 11:13:43.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:
Versions:13.13.0 Frequency of
Occurrence		Occasional
Related
Issues:
Environment:LinuxAttachments:( 0) backtrace.txt
( 1) full_backtrace.txt
Description:During a call rtcp report is sent and received to get the info about the call quality. After that taskprocessor is scheduled to destroy all the user data. At that time rtcp message payload destructor is also called to destroy the rtcp report. Sometimes on it's destruction  abort signal is issued which result in crash of asterisk.
Comments:By: Asterisk Team (asteriskteam) 2017-10-11 01:47:00.183-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: Richard Mudgett (rmudgett) 2017-10-11 08:12:36.100-0500

Your backtrace appears to contain a memory corruption. We need one or both of the following items to continue investigation of the issue:
1. Valgrind output. See https://wiki.asterisk.org/wiki/display/AST/Valgrind for instructions on how to use Valgrind with Asterisk.
2. MALLOC_DEBUG output. See https://wiki.asterisk.org/wiki/display/AST/MALLOC_DEBUG+Compiler+Flag for instructions on how to use the MALLOC_DEBUG option.

Note that MALLOC_DEBUG and Valgrind are mutually exclusive options. Valgrind output is preferable, but will be more system resource intensive and may be difficult to get on a production system. In such a case, you may have better luck getting the necessary output from MALLOC_DEBUG.

There have been a few memory corruption fixes since v13.13.0 so this may already be fixed.
By: Asterisk Team (asteriskteam) 2017-10-25 12:00:01.888-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