[Home]

Summary:ASTERISK-27235: Crash when freeing frame in bridge
Reporter:Richard Kenner (kenner)Labels:
Date Opened:2017-08-30 17:58:49Date Closed:2017-09-07 18:19:39
Priority:MajorRegression?
Status:Closed/CompleteComponents:Core/Bridging
Versions:14.6.0 Frequency of
Occurrence
Related
Issues:
duplicatesASTERISK-27238 Bridging: Crash freeing a frame that's already been freed
Environment:Centos *Attachments:( 0) traceback.txt
Description:I have a crash in freeing a frame, called from bridge_frame_free.  This was a three-way video conference between a Polycom Trio and two Linphone Desktop applications.  The full traceback is in traceback.txt.

Comments:By: Asterisk Team (asteriskteam) 2017-08-30 17:58:50.057-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 Kenner (kenner) 2017-08-30 18:25:35.415-0500

Oh, the frame is:

{noformat}
(gdb) print *fr
$1 = {frametype = 671088760, subclass = {integer = 671088760,
   format = 0x1ada980, frame_ending = 0}, datalen = 0, samples = 640,
 mallocd = 1, mallocd_hdr_len = 215, offset = 64,
 src = 0x7f092800d7c8 "siren14tolin32", data = {ptr = 0x0, uint32 = 0,
   pad = "\000\000\000\000\000\000\000"}, delivery = {tv_sec = 1504129163,
   tv_usec = 810700}, frame_list = {next = 0x0}, flags = 0, ts = 0, len = 0,
 seqno = 0}
{noformat}
By: Rusty Newton (rnewton) 2017-09-06 17:15:07.663-0500

Richard, is this a one-time crash or reproducible?

Also, do you have a log that accompanied the crash?
By: Richard Kenner (kenner) 2017-09-06 17:22:32.604-0500

It happened more than once, but is not reproducable at will.  I did not save the log.  I'm assuming that is the same issue as ASTERISK-27238, especially once I saw the valgrind error.  So perhaps best to close this as a duplicate of that.
By: Rusty Newton (rnewton) 2017-09-07 18:22:10.648-0500

Thanks Richard.