[asterisk-bugs] [JIRA] (ASTERISK-28633) stasis bridge topic leak

[Benjamin Keith Ford (JIRA)]

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

Benjamin Keith Ford commented on ASTERISK-28633:
------------------------------------------------

I'm going to go ahead and open an issue for this, as it does look like it's a valid issue. When a developer starts working on it, they may need more information, and will ask here. Until then, can you describe the general use of the system to help determine which paths the code might be taking to help narrow down where the topic is not being cleaned up?

> stasis bridge topic leak
> ------------------------
>
>                 Key: ASTERISK-28633
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28633
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_stasis
>    Affects Versions: 17.0.1
>         Environment: We are running Asterisk 17 on Debian Buster. The asterisk is hadling only basic calls by AGI and FastAGI. Dial is done only by app_dial.
>            Reporter: Joeran Vinzens
>            Assignee: Unassigned
>            Severity: Minor
>         Attachments: asterisk_output_2.txt, asterisk_output.txt
>
>
> It seems after a call had been cleared up there is no cleanup of the bridge topic within the stasis bus. After starting the asterisk there is no bridge topic according "stasis show topics". When running normal call load with us at the end of a day we collected as many Bridge topics as we have processed calls. "show topics" after a day shows about 48000 open bridge topics but only 150 channel topics according the ongoing calls.
> It seems there is nothing deleting the bridge topics.
> So far we have no negative side effects like load or memory but we are restarting the asterisk frequently. 



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