| Summary: | ASTERISK-26792: Lock inversion between channel hangup and the bridging code | ||||
| Reporter: | Ross Beer (rossbeer) | Labels: | |||
| Date Opened: | 2017-02-14 08:09:05.000-0600 | Date Closed: | 2017-02-14 08:46:29.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Channels/General | ||
| Versions: | GIT | Frequency of Occurrence | Frequent | ||
| Related Issues: |
| ||||
| Environment: | Attachments: | ( 0) core.7674-brief_clean.txt | |||
| Description: | Asterisk deadlocks and all process stops waiting for the lock to be released.
| ||||
| Comments: | By: Asterisk Team (asteriskteam) 2017-02-14 08:09:06.691-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: George Joseph (gjoseph) 2017-02-14 08:27:08.068-0600 The backtraces contain sensitive information and I have them. | ||||