| Summary: | ASTERISK-19009: Deadlock on sip_new and load_realtime_queue. | ||||
| Reporter: | Steven Wheeler (swheeler) | Labels: | |||
| Date Opened: | 2011-12-12 15:52:59.000-0600 | Date Closed: | 2011-12-14 08:29:03.000-0600 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Applications/app_queue Channels/chan_sip/General | ||
| Versions: | Frequency of Occurrence | One Time | |||
| Related Issues: |
| ||||
| Environment: | CentOS release 5.7 (Final), Asterisk 1.8.7.1 with MySQL as the real time configuration back end. | Attachments: | ( 0) backtrace.txt ( 1) backtrace-full.txt ( 2) core-show-locks-20111212.txt | ||
| Description: | From what I can tell it looks like asterisk deadlocked while processing a new SIP channel and loading a queue's configuration from the real time database. In the uploaded core-show-locks-20111212 file the two threads that deadlocked are 0x42e49940 and 0x41dd8940. Please let me know if there is any more information you need to debug this problem. | ||||
| Comments: | By: Steven Wheeler (swheeler) 2011-12-12 15:53:24.618-0600 Output of asterisk -rx 'core show locks' By: Steven Wheeler (swheeler) 2011-12-12 15:55:31.283-0600 Output of gdb thread apply all bt By: Steven Wheeler (swheeler) 2011-12-12 15:56:29.488-0600 Output of gdb thread apply all bt full By: Steven Wheeler (swheeler) 2011-12-12 15:57:16.631-0600 Please note that the core file was generated using kill so the segfault is not related to this issue. By: Richard Mudgett (rmudgett) 2011-12-12 17:14:48.256-0600 This appears to be the same deadlock as ASTERISK-18740. Or at least the fix should also fix this deadlock. By: Steven Wheeler (swheeler) 2011-12-13 09:51:44.449-0600 Any idea when the fix will make it into a release? By: Richard Mudgett (rmudgett) 2011-12-13 10:05:52.102-0600 The fix for ASTERISK-18740 will be in v1.8.9. By: Matt Jordan (mjordan) 2011-12-14 08:29:03.770-0600 I'm going to go ahead and close this issue as it is a duplicate of ASTERISK-18740. If you test with the 1.8 branch (which is slated to become 1.8.9.0) and find that the deadlock still occurs, please reopen this issue. | ||||