[asterisk-bugs] [JIRA] (ASTERISK-24938) ARI Snoop Channel eventually consumes entire CPU

[George Ladoff (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Ladoff updated ASTERISK-24938:
-------------------------------------

    Assignee: Rusty Newton  (was: George Ladoff)
      Status: Triage  (was: Waiting for Feedback)

Debug log attached. 

I started the logger, called into the extension that sends to Stasis, used a REST client to list the channel ID, use the REST client to start Snoop, let it run for 10 minutes, used the REST client delete the Snoop channel, rotated the log.

> ARI Snoop Channel eventually consumes entire CPU
> ------------------------------------------------
>
>                 Key: ASTERISK-24938
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24938
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_stasis, Resources/res_ari_channels
>    Affects Versions: 13.2.0, 13.3.0
>         Environment: Ubuntu Linux 14.04.2, Asterisk built from source, Realtime with MySQL
>            Reporter: George Ladoff
>            Assignee: Rusty Newton
>         Attachments: issue_24938_full_log.txt
>
>
> When I create a Snoop Channel with ARI, the thread immediately begins to consume an additional 2-3% CPU per minute. By about 40 minutes, an entire 3Ghz CPU is consumed. 
> To recreate this, simply have any channel in Stasis then create a Snoop channel from the original channel. CPU usage will start escalating right away.
> I'm specifically creating channels with Spy Out but I've tried both directions and Whisper with the same result.
> This happens every time a Snoop channel is created. The Stasis application and all of the channels are still usable, but only until all of the CPU is consumed. Then of course nothing works. 
> Once the Snoop channel is deleted, the usage goes immediately back to normal (sustained 1-2% per thread). 
> I've tried snooping channels that are using a variety of codecs: ulaw, gsm, g.729. All have the same result. 
> This happens whether the Snoop channel is then bridged or recorded or neither.
> I've tried with both Timerfd and pthread.



--
This message was sent by Atlassian JIRA
(v6.2#6252)