[asterisk-dev] File handle leaks using meetme - Asterisk 1.4, dahdi 2.5.0.2

[Olle E. Johansson]

8 mar 2012 kl. 14:51 skrev Kevin P. Fleming:

> On 03/08/2012 04:29 AM, Olle E. Johansson wrote:
>> 
>> 8 mar 2012 kl. 11:18 skrev Olle E. Johansson:
>> 
>>> Coming back to an earlier discussion, I've now have confirmed that our usage of Meetme's leaks file handles. On one system that operates up to 450 concurrent meetme's I now have 718 open file handles in /dev/dahdi that stayed for more than 24 hours  - even though during night we have no meetme's at all. This number grows every night. Of the 718, 654 is /dev/dahdi/pseudo and the rest are /dev/dahdi/timer.
>>> 
>>> I am suspecting a masquerade issue since we use a manager transfer to get the last participant out of every meetme. Trying to set up a test for that.
>>> 
>>> Anyone else that have seen similar issues?
>> 
>> Found an issue in Jira:
>> https://issues.asterisk.org/jira/browse/ASTERISK-10894
>> 
>> This was never applied to 1.4 even though we have a patch for it in the bug report.
> 
> Well, that's quite odd. There's no reason that patch should not have been applied to all release branches at that time that had the problem, and 1.4 certainly did.

I realize that the patch only takes care of dahdi/pseudo and not dahdi/timer and I have leaks in both. Trying to figure out where we allocate the timers and how they're connected to the ast_chan structure. Your earlier long educational mail about meetme and files only covered the pseudo channels ;-)

Still testing various scenarious to figure out which type of call that leaks.

/O