Summary:	ASTERISK-26946: Crash as the user leaves the conference when the video frame is distributed
Reporter:	junxu (nightkids)	Labels:
Date Opened:	2017-04-16 21:54:22	Date Closed:	2020-01-14 11:14:13.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	. I did not set the category correctly.
Versions:	13.1.0	Frequency of Occurrence	Occasional
Related Issues:
Environment:	centOS 6.5	Attachments:
Description:	when the src distribution the video frame to others in the confbridge，another user leave，it will crash。（join and leave confbridge was very frequently use sipp） the crash back trace was like that： {noformat} (gdb) bt #0  ast_bridge_queue_everyone_else (bridge=<value optimized out>, bridge_channel=0x1dec7a8, frame=0x7f8f58c619f0) at bridge_channel.c:1108 #1  0x00007f8f6e05a2cc in softmix_bridge_write_video (bridge=0x1e3fb28, bridge_channel=<value optimized out>, frame=0x7f8f58c619f0)    at bridge_softmix.c:561 #2  softmix_bridge_write (bridge=0x1e3fb28, bridge_channel=<value optimized out>, frame=0x7f8f58c619f0) at bridge_softmix.c:705 #3  0x00007f8f6d42b127 in send_pic (data=0x675efc8) at app_confbridge.c:9084 #4  0x0000000000591bad in ast_sched_runq (con=0x7f8f4748e230) at sched.c:625 #5  0x00000000005920c1 in sched_run (data=0x7f8f4748e230) at sched.c:140 #6  0x00000000005c46ab in dummy_start (data=<value optimized out>) at utils.c:1232 #7  0x0000003b210079d1 in start_thread () from /lib64/libpthread.so.0 #8  0x0000003b20ce8b6d in clone () from /lib64/libc.so.6 {noformat} BTW，i want know why the bridge->channels didn't have the lock,it will operate by muti threads,that's Make me wonder.
Comments:	By: Asterisk Team (asteriskteam) 2017-04-16 21:54:23.414-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Richard Mudgett (rmudgett) 2017-04-17 09:50:13.907-0500 You appear to be using a modified version of app_confbridge as there is no function named send_pic() in the the code.  Also Asterisk v13.1.0 is more than two years old at this point. By: junxu (nightkids) 2017-04-18 01:57:38.637-0500 3Q for your response，the app_confbridge was modified by others.i will use the latest version to check this issue. thank you! By: Rusty Newton (rnewton) 2017-04-18 09:23:58.706-0500 Thank you for the crash report. However, we need more information to investigate the crash. Please provide: 1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1]. 2. Specific steps taken that lead to the crash. 3. All configuration information necesary to reproduce the crash. Thanks! [1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Rusty Newton (rnewton) 2017-04-18 09:26:36.818-0500 If the issue occurs in the latest version of your branch then: 1. Provide a new backtrace following the instructions linked in my previous comment. 2. Provide a debug log following: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information Thanks! By: Asterisk Team (asteriskteam) 2017-05-02 12:00:02.012-0500 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