Summary:ASTERISK-21639: Segfault in app_confbridge while stress testing
Reporter:Robert McGilvray (rmcgilvray)Labels:
Date Opened:2013-04-18 12:56:30Date Closed:2018-01-02 08:44:29.000-0600
Versions:11.4.0 Frequency of
Environment:Redhat EL 6.4 kernel 2.6.32-358.2.1.el6.x86_64Attachments:( 0) backtrace.txt
( 1) confbridge-profiles.txt
( 2) dialplan-ael.txt
( 3) messages.gz
Description:Asterisk Segfaults during stress testing against ConfBridge. It seems to be triggered by a combination of admin/marked and nonadmin/unmarked joining and leaving a single conference.

It is easily reproduced using SIPP with 100 calls. I've included the dialplan but essentially 100 calls are generated, half use an admin profile and the other half a participant. They are randomly joining 64 bridges for 30s and it crashes every time.

Program terminated with signal 11, Segmentation fault.
#0  0x00007f699bac0d91 in conf_remove_user_waiting (conference_bridge=0x7f690805aeb8, cbu=0x7f6980681fc0) at app_confbridge.c:3060
3060    AST_LIST_REMOVE(&conference_bridge->waiting_list, cbu, list);
#0  0x00007f699bac0d91 in conf_remove_user_waiting (conference_bridge=0x7f690805aeb8, cbu=0x7f6980681fc0) at app_confbridge.c:3060
       __prev = 0x6361632f6266636f
       __elm = 0x7f6980681fc0

Comments:By: Robert McGilvray (rmcgilvray) 2013-04-18 12:59:32.909-0500

Confbridge profiles, dialplan and verbose/debug output.

By: Robert McGilvray (rmcgilvray) 2013-04-18 13:00:49.816-0500


By: Robert McGilvray (rmcgilvray) 2013-05-28 10:00:47.243-0500


Any chance this could be assigned to someone? I know things are done on priority so I understand completely.

I'd like to move forward with replacing our Meetme implementation and this bug is a show stopper.


By: Walter Doekes (wdoekes) 2013-05-29 07:52:21.634-0500

{{/home/asterisk/gocfb/cache/sounds}} is written on top of 0x6361632f6266636f. ("ocfb/cac")

Can you reproduce with MEMORY_DEBUG on?

By: Joshua C. Colp (jcolp) 2017-12-18 12:03:41.549-0600

Is this a problem under the current supported versions of Asterisk? Locking was changed and tweaked some which may have resolved it.

By: Asterisk Team (asteriskteam) 2018-01-02 08:44:29.368-0600

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines