| Summary: | ASTERISK-18704: Asterisk deadlock | ||
| Reporter: | Dalius M. (mdalius) | Labels: | |
| Date Opened: | 2011-10-11 06:29:12 | Date Closed: | 2011-11-01 08:54:52 |
| Priority: | Critical | Regression? | |
| Status: | Closed/Complete | Components: | |
| Versions: | 1.6.2.20 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Linux 2.6.32-5-686 #1 SMP Tue Mar 8 21:36:00 UTC 2011 i686 GNU/Linux Asterisk compiled from source | Attachments: | ( 0) backtrace-threads.txt ( 1) core-show-locks.txt |
| Description: | Sometimes Asterisk produces deadlocks. When this happens we can connect to CLI, but "core restard now" does nothing. We must kill Asterisk process and start Asterisk again | ||
| Comments: | By: Leif Madsen (lmadsen) 2011-11-01 08:54:52.302-0500 This doesn't appear to be an actual deadlock, but rather another issue where the usage of res_timing_pthread causes what APPEARS to be a deadlock, but is really just the channel waiting for something to return for quite a long time. Please use res_timing_dahdi or res_timing_timerfd (version 1.8.7.0 or later) and it should resolve the problem. Do not use res_timing_pthread. | ||