[asterisk-bugs] [JIRA] (ASTERISK-30432) res_speech_aeap: Tight loop; high CPU usage

[Peter Howell (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-30432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261415#comment-261415 ] 

Peter Howell commented on ASTERISK-30432:
-----------------------------------------

It's played in a GoSub routine; not in a hangup handler.

Can we call SpeechDestroy in a hangup handler?  Since the call ends abruptly, this isn't called, so I'm wondering if calling it in a hangup handler is possible and might clean things up.

> res_speech_aeap: Tight loop; high CPU usage
> -------------------------------------------
>
>                 Key: ASTERISK-30432
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30432
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/NewFeature
>    Affects Versions: 18.16.0
>         Environment: CentOS-7 3.10.0-1160.76.1.el7.x86_64
>            Reporter: Peter Howell
>            Assignee: Peter Howell
>         Attachments: asterisk-open-files.txt, core-asterisk-running-2023-02-20T17-18-13Z-brief.txt, core-asterisk-running-2023-02-20T17-18-13Z-full.txt, core-asterisk-running-2023-02-20T17-18-13Z-info.txt, core-asterisk-running-2023-02-20T17-18-13Z-locks.txt, core-asterisk-running-2023-02-20T17-18-13Z-thread1.txt, dump.pcap
>
>
> We see that on occasion closed AEAP connections to Asterisk are not closing.  We are sending an OP_CLOSE before closing the connection, but it seems under certain conditions, the connection does not close.  At this point, Asterisk goes into a tight loop on these zombie connections and the result is high CPU usage.



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