Summary:ASTERISK-19834: Memory leak caused by thread created by bridge_channel_join being neither joined nor detached
Reporter:Marcus Hunger (fnordian)Labels:
Date Opened:2012-05-03 05:23:17Date Closed:2012-07-06 10:23:20
Versions:10.3.1 Frequency of
Environment:linux/debian squeeze ia32Attachments:( 0) bridge.patch
Description:There is a memory leak caused by not cleaning up threads created by bridge_channel_join.
Comments:By: Marcus Hunger (fnordian) 2012-05-03 10:52:43.021-0500

patch creates bridge-thread detached so it does not have to be joined

By: Mark Michelson (mmichelson) 2012-07-05 15:36:04.840-0500

My initial reaction to the patch is that it's not going to be good enough due to how the smart_bridge_operation works. It attempts to join the bridge thread before moving further with its operations. I think the way to go here is to keep the thread joinable but to make sure the thread gets joined when the bridge is no longer being used.

By: Mark Michelson (mmichelson) 2012-07-05 18:26:54.766-0500

If you're interested, I've posted my own fix for this on review board at https://reviewboard.asterisk.org/r/2012