]> git.ipfire.org Git - thirdparty/asterisk.git/commit
bridge: avoid leaking channel during blond transfer
authorScott Griepentrog <sgriepentrog@digium.com>
Fri, 19 Dec 2014 17:26:34 +0000 (17:26 +0000)
committerScott Griepentrog <sgriepentrog@digium.com>
Fri, 19 Dec 2014 17:26:34 +0000 (17:26 +0000)
commit6a99df47c09e9d9f51ea6afba76b259832eadb51
tree59c85814f67aabfdacf6167e06a3cec649203425
parentb22c833c12d69a84fd6e6d33f4529fbc6e37dd47
bridge: avoid leaking channel during blond transfer

After a blond transfer (start attended and hang up)
to a destination that also hangs up without answer,
the Local;1 channel was leaked and would show up on
core show channels.  This was happening because the
attended state blond_nonfinal_enter() resetting the
props->transfer_target to null while releasing it's
own reference, which would later prevent props from
releasing another reference during destruction. The
change made here is simply to not assign the target
to NULL.

ASTERISK-24513 #close
Reported by: Mark Michelson
Review: https://reviewboard.asterisk.org/r/4262/
........

Merged revisions 429826 from http://svn.asterisk.org/svn/asterisk/branches/12

git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/13@429827 65c4cc65-6c06-0410-ace0-fbb531ad65f3
main/bridge_basic.c