On Wed, Dec 1, 2010 at 12:15 PM, Kevin P. Fleming <kpflem...@digium.com>wrote:

> On 12/01/2010 01:05 PM, Steve Murphy wrote:
> > Hello,
> >
> > I wonder if anyone else has noticed this.
> >
> > I see a pair of calls to pipe() within the codec_g729a, and suddenly, I
> > have a leaked file descriptor that remains until asterisk dies.
> >
> >
>
--snip--

> > So, since there is no list of problems fixed with the current g729a
> > module distribution, (at least, no in the README in the dist,
> > is this a problem that is known? Is this a new problem? Should I call
> > support?
> >
> > Anybody else see this?
>
> This problem may be in the license file checking code... I've just taken
> a quick look at it, and there may be at least one code path that leaks a
> pair of pipe file descriptors. I'll enter an internal issue to get this
> addressed ASAP. Thanks for the report.
>
>
Kevin--

Any estimates on how long it will take to seal the leak?
Need a beta tester?

murf


Steve Murphy

ParseTree Corp.

57 Lane 17

Cody, WY 82414

✉  m...@parsetree.com

☎ 307-899-5535
-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
               http://www.asterisk.org/hello

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

Reply via email to