Summary:	ASTERISK-25547: Asterisk crashed when user came in confbridge
Reporter:	Dmitry Burilov (netaskd)	Labels:
Date Opened:	2015-11-11 11:07:10.000-0600	Date Closed:	2016-05-06 12:04:28
Priority:	Critical	Regression?
Status:	Closed/Complete	Components:	Applications/app_confbridge
Versions:	11.7.0	Frequency of Occurrence	Occasional
Related Issues:
Environment:	CentOS release 6.4 (Final) 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 00:31:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux	Attachments:	( 0) backtrace.txt ( 1) backtrace1.txt.tar.gz ( 2) backtrace2.txt.tar.gz
Description:	Time to time asterisk crashed when user come in conference (application confbridge).
Comments:	By: Asterisk Team (asteriskteam) 2015-11-11 11:07:11.270-0600 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: Dmitry Burilov (netaskd) 2015-11-11 11:31:07.507-0600 backtraces By: Rusty Newton (rnewton) 2015-11-11 15:55:34.669-0600 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected and the location of documentation that led you to that expectation. 3. The behavior you actually encountered. To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines [2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information Additionally I can't unpack the tar.gz archive for an unknown reason. Please attach your backtraces as simply .txt . They should be very small.. By: Asterisk Team (asteriskteam) 2015-11-26 12:00:22.025-0600 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 By: Dmitry Burilov (netaskd) 2016-02-09 09:09:09.691-0600 I'm sorry for delay. Backtrace below [Edit by Rusty - Removed and attaching to the issue as requested] By: Asterisk Team (asteriskteam) 2016-02-09 09:09:10.245-0600 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Rusty Newton (rnewton) 2016-04-06 19:14:43.831-0500 I'm also sorry about the delay on this one, it slipped through the cracks. Did you have any verbose/debug logs available from the time of crash? or a recent crash if you are still encountering the problem? By: Rusty Newton (rnewton) 2016-04-07 15:59:30.640-0500 It also appears there could be an issue with the trace {noformat} warning: Source file is more recent than executable. {noformat} Can you update your source or binary to match and then provide a new trace when the issue occurs again? Along with the trace, please provide an Asterisk debug log if possible: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Asterisk Team (asteriskteam) 2016-04-22 12:00:00.886-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 By: Asterisk Team (asteriskteam) 2016-05-06 12:00:01.324-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