Summary:	ASTERISK-18231: asterisk crashes when doing multiple ConfBridge
Reporter:	Rilke Petrosky Ulloa (xenomuta)	Labels:	confbridge crash mutex pthread
Date Opened:	2011-08-06 19:42:04	Date Closed:	2011-11-07 11:05:51.000-0600
Priority:	Critical	Regression?
Status:	Closed/Complete	Components:	Applications/app_confbridge
Versions:	1.8.5.0	Frequency of Occurrence	Frequent
Related Issues:
Environment:	8 x Intel(R) Xeon(R) CPU E31280 @ 3.50GHz, 16G RAM, Ubuntu Server 10.04 Linux Kernel 2.6.32-33-preempt	Attachments:	( 0) backtrace.txt
Description:	Asterisk crashes (Segmentation fault 11) unexpectedly right after consumming ridiculous ammount of CPU load when doing ConfBridge and simple dialplans arround 120 calls. I have a couple of core dumps, their backtrace point to something related with pthreads and mutex: GDB backtrace: Core was generated by `/usr/sbin/asterisk -f -vvvg -c'. Program terminated with signal 11, Segmentation fault. #0  0x00007f68a5db53c4 in pthread_mutex_lock () from /lib/libpthread.so.0 (gdb) bt #0  0x00007f68a5db53c4 in pthread_mutex_lock () from /lib/libpthread.so.0 #1  0x00007f6891580276 in bridge_write (ast=0x7f67ac43a118, f=0x4285ac8) at chan_bridge.c:98 #2  0x0000000000475dbc in ast_write (chan=0x7f67ac43a118, fr=0x4285ac8) at channel.c:5049 #3  0x00007f689b4572a9 in softmix_bridge_write (bridge=0x7f67ac462b78, bridge_channel=0x7f66581bd988, frame=0x7dc580)    at bridge_softmix.c:585 #4  0x000000000044ac81 in ast_bridge_handle_trip (bridge=0x7f67ac462b78, bridge_channel=0x7f66581bd988,    chan=<value optimized out>, outfd=<value optimized out>) at bridging.c:318 #5  0x000000000044b1e4 in bridge_channel_join_multithreaded (bridge_channel=0x7f66581bd988) at bridging.c:756 #6  bridge_channel_join (bridge_channel=0x7f66581bd988) at bridging.c:974 #7  0x000000000044c429 in bridge_channel_thread (data=0x0) at bridging.c:1112 #8  0x0000000000553f5b in dummy_start (data=<value optimized out>) at utils.c:1010 #9  0x00007f68a5db29ca in start_thread () from /lib/libpthread.so.0 #10 0x00007f68a689070d in clone () from /lib/libc.so.6 #11 0x0000000000000000 in ?? ()
Comments:	By: Malcolm Davenport (mdavenport) 2011-08-08 08:13:38.702-0500 Do you see the same behavior on the ConfBridge application that's a part of Asterisk 10? By: Rilke Petrosky Ulloa (xenomuta) 2011-08-08 08:50:10.913-0500 Yes, I've tried updating and other revisions too. BTW, I did not upload the coredumps, because it is 8.8GB long and gzips to 41MB, sorry. By: Richard Mudgett (rmudgett) 2011-08-08 09:42:33.243-0500 Excerpt from https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace Don't attach core files on the bug tracker as they are only useful on the machine they were generated on. We only need the output of the 'bt' and 'bt full.' By: Leif Madsen (lmadsen) 2011-08-08 12:48:08.298-0500 Marking as Request Feedback until the reporter is able to generate a backtrace per the wiki guidelines. Thanks! By: Rilke Petrosky Ulloa (xenomuta) 2011-08-08 13:21:35.011-0500 backtrace By: Rilke Petrosky Ulloa (xenomuta) 2011-08-08 13:22:14.362-0500 bt full By: Leif Madsen (lmadsen) 2011-08-09 09:05:07.227-0500 Your backtraces contain <value optimized out> which means your backtraces are optimized. Please compile your Asterisk per the wiki guidelines and provide an unoptimized backtrace. Thanks! By: Rilke Petrosky Ulloa (xenomuta) 2011-08-09 10:01:33.965-0500 Ok, I will have to move callers to a backup server while I compile and install this way. This is a system in production By: Rilke Petrosky Ulloa (xenomuta) 2011-08-09 14:41:30.137-0500 The backtrace the way expected, by the way, that totally maxed out cpu usage to 100% By: Rilke Petrosky Ulloa (xenomuta) 2011-08-17 21:02:46.341-0500 Is this information enough or correct to have further knowledge of this problem? By: Paul Belanger (pabelanger) 2011-10-10 15:09:55.369-0500 Thank you for your bug report. In order to move your issue forward, we require a backtrace[1] from the core file produced after the crash. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then: make install After enabling, reproduce the crash, and then execute the backtrace[1] instructions. When complete, attach that file to this issue report. [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Leif Madsen (lmadsen) 2011-11-07 11:05:46.043-0600 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines