Summary: | ASTERISK-17512: Asterisk-deadlocks - followup to #18497 | ||||||
Reporter: | Marcin Kowalczyk (kowalma) | Labels: | |||||
Date Opened: | 2011-03-04 02:14:49.000-0600 | Date Closed: | 2013-04-08 15:38:04 | ||||
Priority: | Minor | Regression? | No | ||||
Status: | Closed/Complete | Components: | Channels/chan_sip/General Resources/res_timing_timerfd | ||||
Versions: | 1.8.2 | Frequency of Occurrence | |||||
Related Issues: |
| ||||||
Environment: | Attachments: | ( 0) backtrace-threads.txt ( 1) core-show-locks.txt | |||||
Description: | Ticket ASTERISK-17129 introduced patch for dead-locks. I have applied it but I still get deadlocks. | ||||||
Comments: | By: Marcin Kowalczyk (kowalma) 2011-03-08 13:24:29.000-0600 I think this is somehow reated to pthread timing, as when I changed timing to dahdi problem did not re-occur. By: Matt Jordan (mjordan) 2013-04-08 15:37:34.821-0500 This appears to have been related to ASTERISK-17407 and/or ASTERISK-17867. Per Leif, this was fixed in 1.8.7.0. As such, I'm closing this out - if you find that you're still experiencing a problem with {{res_timing_timerfd}}, please contact a bug marshal in #asterisk-bugs and we'll be happy to reopen this issue. Thanks! |