[asterisk-bugs] [JIRA] (ASTERISK-22421) Local channels in a ConfBridge w/ jitterbuffer=yes leak ast_frame's after masquerade

[Rusty Newton (JIRA)]

Rusty Newton created ASTERISK-22421:
---------------------------------------

             Summary: Local channels in a ConfBridge w/ jitterbuffer=yes leak ast_frame's after masquerade
                 Key: ASTERISK-22421
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22421
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Applications/app_confbridge, Channels/chan_local, Core/Jitterbuffer, Core/ManagerInterface
    Affects Versions: 11.6.0
            Reporter: Corey Farrell


I use AMI to originate calls into MeetMe.  I've recently started testing with ConfBridge, but found a memory leak that prevents me from switching.  Using Asterisk 11.

To replicate:
* Use attached configuration - extensions.conf, confbridge.conf
* Set dialplan global MYDEVICE as appropriate
* Start asterisk in valgrind - MALLOC_DEBUG might work I haven't tried
* Call the ConfBridge - don't make MYDEVICE unavailable
* Using AMI send action Originate - see ami-action.txt
* Ensure the destination call is answered - this causes Local to optimize away

Once the Local channel is optimized away, ast_frame leaks are guaranteed:
* The masquerade/optimize of Local to SIP results in a couple leaks every time.
* AMI: Redirect and Hangup both result in a leak every time.
* Unknown additional trigger sometimes causes huge number of leaked frames.  Leaks 200k in very short time.  Still trying to find a way to reliably reproduce this one.

Changing the Originate channel to 'Local/s at test-out/n' seems to prevent the leaks.  Another strange note, ringing audio is clear but once the masquerade happens the audio quality is terrible.  Either preventing the optimize or turning off jitterbuffer seams to result in good quality audio.

This issue might be related to [ASTERISK-21144].

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira