[asterisk-bugs] [JIRA] (ASTERISK-29037) segfault in opus codec stats transmission

[Andrew Yager (JIRA)]

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

Andrew Yager commented on ASTERISK-29037:
-----------------------------------------

A little further to this - it seems that this bug is only triggered when there is a massive number of TCP sessions being set up/established around the same time, such as immediately after an asterisk restart. The major issue with this is that a restart (due to an intended restart, or as a result of an unexpected crash) could trigger an Opus call to attempt to send its telemetry which fails, possibly because something else is going on somewhere else in libcurl.

I've left asterisk stable for 5 - 10 minutes and then triggered an Opus call and have not been able to replicate the crash in that case; but if I restart Asterisk within the first 2 - 3 minutes after a restart while all the peers are qualifying, and then start an Opus call the segfault will trigger.

> segfault in opus codec stats transmission
> -----------------------------------------
>
>                 Key: ASTERISK-29037
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29037
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Codecs/codec_opus
>    Affects Versions: 13.35.0
>         Environment: Centos 7.8
>            Reporter: Andrew Yager
>            Severity: Minor
>         Attachments: core.6345-brief.txt, core.6345-thread1.txt
>
>
> Apparently during codec decrease count and license usage telemetry, we see a segfault generated. 



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