[asterisk-bugs] [JIRA] (ASTERISK-29882) Occasional segfaults in production

[Kevin Harwell (JIRA)]

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

Kevin Harwell commented on ASTERISK-29882:
------------------------------------------

Ah yeah ha I posted without refreshing so missed your update.

It is indeed NULL! I do wonder though why it didn't crash on the earlier call to {{ast_channel_uniqueid}}.

I'll open the issue. Not sure when it'll be looked into though. The fastest way to a fix is by submitting a patch :-) (if you're interested)

Since it is NULL a NULL check in that function before accessing the variable should keep it from crashing. So if you wanted to avoid crashes you could patch the code to do such. However, without someone looking more into I don't know the full reprecussions of doing such. For instance, if that information does not exist should the message be published? Or should it be published without said data? Or perhaps should it be always guranteed that data exists before that function is called? etc...

> Occasional segfaults in production
> ----------------------------------
>
>                 Key: ASTERISK-29882
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29882
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 18.8.0
>         Environment: Debian Stretch in Docker
>            Reporter: Duncan
>            Assignee: Unassigned
>            Severity: Critical
>         Attachments: coreFile-thread1.txt, Screenshot from 2021-12-20 09-09-29.png
>
>
> Hi team,
> We are seeing Asterisk instances occasionally segfault in production. This happens in our voicemail handling stasis app, which includes playing media to the caller, and then recording the caller, managed through ARI. We don't know what the steps are to reproduce the issue as we have never reproduced it ourselves, but suspect it is probably some kind of race condition.
> I have attached coreFile-thread1.txt from the core dump. We have all the other core dump *.txt files but would prefer not to post these publicly in case they could contain any sensitive data. I would be happy to provide these directly to a maintainer via email. We’re happy to assist debugging this issue if at all possible, and have some C experience but no experience working on Asterisk. Please get in touch if we can do anything to help troubleshoot further.
> Many thanks



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