| Summary: | ASTERISK-27672: MixMonitor Audiohook SIGSEGV under Load | ||||
| Reporter: | Joshua Elson (joshelson) | Labels: | patch | ||
| Date Opened: | 2018-02-12 19:08:24.000-0600 | Date Closed: | 2018-02-21 17:03:01.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Applications/app_mixmonitor | ||
| Versions: | 15.2.0 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Attachments: | ( 0) c9d6bfc.diff ( 1) core.asterisk-2018-02-12T18-31-22-0500-brief.txt ( 2) core.asterisk-2018-02-12T18-31-22-0500-full.txt ( 3) core.asterisk-2018-02-12T18-31-22-0500-locks.txt ( 4) core.asterisk-2018-02-12T18-31-22-0500-thread1.txt ( 5) core.asterisk-2018-02-12T19-49-30-0500-brief.txt ( 6) core.asterisk-2018-02-12T19-49-30-0500-full.txt ( 7) core.asterisk-2018-02-12T19-49-30-0500-locks.txt ( 8) core.asterisk-2018-02-12T19-49-30-0500-thread1.txt | |||
| Description: | This is proving to be quite reproducible in one of our environments that dials lots of AMI originated outbound calls that are recorded in a MixMonitor session.
Currently not able to completely reproduce in lab environment, but crash is happening 10 or more times today. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2018-02-12 19:08:25.810-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: Joshua Elson (joshelson) 2018-02-12 19:08:46.882-0600 Coredumper output attached. By: Joshua Elson (joshelson) 2018-02-12 19:12:54.880-0600 Second set of traces. By: Joshua C. Colp (jcolp) 2018-02-12 19:17:15.839-0600 This is an already known about security issue which is being released in approximately a week and a half. I've attached a patch which resolves it. | ||||