Summary:ASTERISK-17119: Deadlock after receiving calls generated with sipp
Reporter:Claudio Villalobos (devmod)Labels:
Date Opened:2010-12-16 10:25:00.000-0600Date Closed:2013-01-15 10:54:18.000-0600
Versions:Frequency of
Environment:Attachments:( 0) backtrace-threads.txt
( 1) core_show_locks.txt
( 2) core_show_threads.txt
( 3) core-show-locks.txt
( 4) gdb_thread_apply_all_bt.txt
Description:I was testing asterisk with sipp and I got deadlocks everytime after about 2-3 minutes.

./sipp -d 5000 -i -l 10 -s 1337 -sf uac.xml sip.acme.net -r 5 -rp 1000 --trace_err

Comments:By: cmaj (cmaj) 2010-12-16 12:26:05.000-0600

Similar bad ao2_locks held on 1.8.2-rc1.  Scenario is not with sipp automated load testing, just manually repeated blind transfers, parking, pickup, etc., between several test SIP phones.

EDIT: 1.8.2-rc1

By: cmaj (cmaj) 2010-12-16 16:24:30.000-0600

I opened new bug 18491 (with a patch included) because the deadlocks I saw were really a separate problem.

By: Matt Jordan (mjordan) 2013-01-15 10:54:06.087-0600

The deadlocks that occurred during an indicate operation and device state changes should all be resolved in Asterisk 1.8 and later at this point. If you are still having this problem, please contact a bug marshal in #asterisk-bugs and we'll reopen this issue.