[Home]

Summary:ASTERISK-27234: Crash on hangup
Reporter:Richard Kenner (kenner)Labels:
Date Opened:2017-08-30 17:55:50Date Closed:2017-09-14 14:19:22
Priority:MajorRegression?
Status:Closed/CompleteComponents:Core/Channels
Versions:14.6.0 Frequency of
Occurrence
Related
Issues:
Environment:Centos 7Attachments:( 0) channel.txt
( 1) traceback.txt
Description:I'm testing video in conferences and have a Polycom Trio at one endpoint and two desktops running Linphone as two other endpoints.  I have a crash due to a memory free problem at ast_free(ast_channel_tech_pvt(chan));

The full traceback is in the attached file traceback.txt and the channel contents are in channel.txt.
Comments:By: Asterisk Team (asteriskteam) 2017-08-30 17:55:52.900-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: Rusty Newton (rnewton) 2017-09-01 15:41:59.007-0500

Thanks for the report! In order to maximize efficiently, there are project guidelines for how to report issues. Please read through the Asterisk Issue Guidelines [1]. After reading the guidelines, please clean up this issue so that bug marshals can more easily help you.

In particular:
1. Don't post extensive debug or logs inside the Description or Comment fields.
2. Use the Description field for a description of the issue, referencing *attached* debug with links or notes.
3. Use the Comment fields for discussion regarding the issue.
4. If you need to put a few lines of debug or logs into any field, surround the text with 8noformat* tags to help us read it easily.
5. Attach files with a '.txt' extension where possible so that they can be analyzed futher by bug marshals.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines


By: Rusty Newton (rnewton) 2017-09-01 15:45:24.027-0500

[~kenner], actually do you mind re-formatting all of your recent issues following the previous comment and guidelines:

ASTERISK-27229
ASTERISK-27225
ASTERISK-27224
ASTERISK-27235
ASTERISK-27238
By: Richard Kenner (kenner) 2017-09-01 17:27:04.963-0500

I think I got them all.
By: Rusty Newton (rnewton) 2017-09-06 17:22:55.066-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:27:11.345-0500

I believe this happened twice, but it's possible that it's actually the same issue as ASTERISK-27238 (less likely) or ASTERISK-27229 (more likely).  I can't reproduce it at will and didn't save the log.
By: Rusty Newton (rnewton) 2017-09-14 14:19:22.516-0500

Closing this one out. We took a look and can't identify from the current data any path to investigate. It may be related to one of the other reported crashes but I'm unsure so I'm not going to link it at the moment.