|Summary:||ASTERISK-20261: app_conference cause asterisk coredump|
|Reporter:||Alexander Merkulov (arheops)||Labels:|
|Date Opened:||2012-08-20 12:33:15||Date Closed:||2013-01-21 08:47:15.000-0600|
|Environment:||debian sqeeze||Attachments:||( 0) bt_full.txt|
( 1) verbose.txt
|Description:||We have simple application with dialplan|
client call in and do long conference calls(upto 1-2 hours)
on some point on user join it just hangs.
ever 2-4 hours of operations. numbers of calls are low(usualy <200 processed calls on dump time)
|Comments:||By: Alexander Merkulov (arheops) 2012-08-20 12:36:00.077-0500|
By: Rusty Newton (rnewton) 2012-08-21 17:56:20.634-0500
Can you also provide an Asterisk full log with VERBOSE and DEBUG messages enabled on level 5? https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information
Please attach the log as a file. The log should show up to the moment the crash happens.
By: Rusty Newton (rnewton) 2012-08-21 17:58:34.668-0500
Noticed your backtrace also has values optimized out. Can you gather a backtrace with the compiler flag DONT_OPTIMIZE and BETTER_BACKTRACES enabled? https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
By: Alexander Merkulov (arheops) 2012-08-21 18:02:57.432-0500
no, i can't do debug 5 on production system for 2+hours.
i can't get same on test calls. looks like it only on productional. also i get same core dump on asterisk 1.8.7,1.8.9 on Centos.
my client start think that asterisk is not work at all.
i can include verbose, but it not help much. i can attach more dumps/bt full. on this moment i have 5.
By: Alexander Merkulov (arheops) 2012-08-21 18:03:32.391-0500
By: Alexander Merkulov (arheops) 2012-08-21 18:08:26.485-0500
no.i can't test anymore this issue. so no,i cna't get trace without optimization.
actualy after 24 hours of debug we just moved out and not use anymore this code.
By: Matt Jordan (mjordan) 2012-08-22 09:33:51.523-0500
ConfBridge in Asterisk 1.8 is in 'extended' support, which means that fixes for it come from the Asterisk developer community. More information on module support states can be found here:
Since ConfBridge and the underlying bridging API received significant updates in Asterisk 10 and later, you are highly encouraged to upgrade to those versions of Asterisk if you want to use ConfBridge.
By: Matt Jordan (mjordan) 2013-01-21 08:47:09.124-0600
Upon further inspection, this is a duplicate of ASTERISK-16640. There was a race condition in the bridging API in Asterisk 1.8 (and earlier) that occurred when two channels left the bridge simultaneously. This should now be corrected in r379091.