[asterisk-bugs] [Asterisk 0011892]: G729 decoders not freed after IAX2 call
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu Jan 31 14:50:49 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11892
======================================================================
Reported By: xrg
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 11892
Category: Channels/chan_iax2
Reproducibility: always
Severity: major
Priority: normal
Status: new
Asterisk Version: 1.4.18
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 01-31-2008 14:13 CST
Last Modified: 01-31-2008 14:50 CST
======================================================================
Summary: G729 decoders not freed after IAX2 call
Description:
Early report.
I have verified that in an SIP -> IAX2 call where the SIP leg has g729 and
the IAX2 ilbc + jitterbuffer, the g729 *decoder* is not freed!
As a result, after 2 calls I can see:
> show g729
0/2 encoders/decoders of 20 licensed channels are currently in use
.. while system is idle.
I guess this has to do with recent changes in 1.4.18, since there was
nothing similar in 1.4.17.
======================================================================
----------------------------------------------------------------------
xrg - 01-31-08 14:50
----------------------------------------------------------------------
Must be related to http://bugs.digium.com/view.php?id=11698, it seems there is a
path that will cause
destroy(ast_trans_pvt *) from main/translate.c:139 not to be called after
the flag, thus not freeing the codec.
Issue History
Date Modified Username Field Change
======================================================================
01-31-08 14:50 xrg Note Added: 0081534
======================================================================
More information about the asterisk-bugs
mailing list