[Home]

Summary:ASTERISK-24437: Review implementation of ast_bridge_impart for leaks and document proper usage
Reporter:Scott Griepentrog (sgriepentrog)Labels:
Date Opened:2014-10-17 12:27:55Date Closed:2014-10-28 11:41:41
Priority:MinorRegression?
Status:Closed/CompleteComponents:Core/Bridging
Versions:Frequency of
Occurrence
Constant
Related
Issues:
Environment:Attachments:( 0) ASTERISK-24437-12.diff
Description:When calling ast_bridge_impart, there is different behavior for some early failure cases versus later ones.  This appears to allow for leaking of features passed in.  After reviewing the implementation, a documentation header should be then added to describe what refs should be held, or are consumed, or channels that need to be hung up by the caller and under what conditions, etc., and a quick check made of usage cases to insure they follow the requirements.
Comments:By: Richard Mudgett (rmudgett) 2014-10-20 12:46:58.225-0500

There is only one missing call to {{ast_bridge_features_destroy()}} in {{ast_bridge_impart()}} to consistently destroy the passed in {{features}} parameter.