Summary: | ASTERISK-28108: Deadlock in publish_msg (stasis.c) | ||||
Reporter: | Denis Lebedev (coredumped) | Labels: | |||
Date Opened: | 2018-10-15 08:40:36 | Date Closed: | 2018-10-15 08:47:17 | ||
Priority: | Major | Regression? | |||
Status: | Closed/Complete | Components: | CDR/General | ||
Versions: | 15.4.0 | Frequency of Occurrence | One Time | ||
Related Issues: |
| ||||
Environment: | CentOS Linux 7 (Core) Linux *** 3.10.0-862.2.3.el7.x86_64 #1 SMP Wed May 9 18:05:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Asterisk versions: 15.4.0 | Attachments: | ( 0) gdb.all.bt.txt | ||
Description: | We found a deadlock in {{publish_msg}} function, in particular thread {{Thread 26 (Thread 0x7fee8c505700 (LWP 14769))}} locked the topic {{stasis.c:845}} and stucked at condvar waiting {{stasis.c:816}}. Another 23 threads stucked at locking of the same topic {{stasis.c:845}}.
At the same time we found this entry in the log: {noformat} taskprocessor.c:893: The 'subm:endpoint_topic_all-cached-00000008' task processor queue reached 500 scheduled tasks again. {noformat} GDB info of all threads attached. | ||||
Comments: | By: Asterisk Team (asteriskteam) 2018-10-15 08:40:37.905-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]. |