| Summary: | ASTERISK-27898: Crash at the and of a call | ||||
| Reporter: | Olivier Krief (okrief) | Labels: | |||
| Date Opened: | 2018-06-05 09:33:14 | Date Closed: | 2018-06-05 09:44:07 | ||
| Priority: | Major | Regression? | No | ||
| Status: | Closed/Complete | Components: | Core/Bridging | ||
| Versions: | 13.20.0 | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | Attention, please: installed version is 13.21.0 but JIRA currently forbids it. Debian Stretch on VMWare. Asterisk compiled from source. | Attachments: | ( 0) core-brief.txt ( 1) core-full.txt ( 2) core-locks.txt ( 3) core-thread1.txt ( 4) debug_extract ( 5) syslog_extract | ||
| Description: | Relevant lines from syslog:
Jun 5 15:05:26 localhost asterisk[18036]: == Spawn extension (from-Adista, 0374020300, 1) exited non-zero on 'SIP/Adista-000089b2' Jun 5 15:05:26 localhost asterisk[18036]: > 0x7f96084be9e0 -- Strict RTP switching to RTP target address 10.33.142.16:43330 as source Jun 5 15:05:27 localhost systemd[1]: asterisk.service: Main process exited, code=killed, status=11/SEGV Jun 5 15:05:27 localhost systemd[1]: asterisk.service: Unit entered failed state. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2018-06-05 09:33:15.389-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: Joshua C. Colp (jcolp) 2018-06-05 09:43:56.610-0500 The crash is still the same as ASTERISK-27859 so I'd suggest providing the information there as well. The use of MALLOC_DEBUG probably just changes the timing conditions and makes it easier to happen. | ||||