| Summary: | ASTERISK-26761: SIGSEGV when user joins confbridge with speex and dtx is active | ||||
| Reporter: | Jens Vogler (JensV) | Labels: | |||
| Date Opened: | 2017-01-31 08:36:58.000-0600 | Date Closed: | 2020-01-14 11:14:11.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | |||
| Versions: | 13.10.0 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | Ubuntu Yakkety | Attachments: | ( 0) backtrace1.txt | ||
| Description: | I am developing a SIP App and whenever a certain combination of devices/users connect to the Asterisk server it crashes instantly with a Segfault. This only occurs when we are using speex and either dtx or pp_vad (with preprocess) is enabled.
I've not been able to pointpoint exactly what the cause of this error is and what is needed to be reproduced. After some further investigation, it seems to happen when two users join the same ConfBridge conference. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2017-01-31 08:37:00.056-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: Jens Vogler (JensV) 2017-01-31 08:37:37.829-0600 Backtrace of the crash happening By: Rusty Newton (rnewton) 2017-01-31 14:29:05.470-0600 Thank you for the crash report. However, we need more information to investigate the crash. Please provide: 1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1]. 2. Specific steps taken that lead to the crash. 3. All configuration information necesary to reproduce the crash. Thanks! [1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Rusty Newton (rnewton) 2017-01-31 14:29:17.028-0600 We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Rusty Newton (rnewton) 2017-01-31 14:30:43.257-0600 I posted two comments with instructions on how to gather a backtrace and debug log. We need the backtrace gathered as per the instructions, with the correct compiler flags and other details, along with the debug log. Attach them both to the issue separately with .txt extensions. Thanks Jens! By: Asterisk Team (asteriskteam) 2017-02-15 12:00:01.935-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: Kirsty Tyerman (ktyerman) 2017-03-16 17:57:32.319-0500 Have had the same issue. Please see ASTERISK-26880 | ||||