[asterisk-bugs] [JIRA] (ASTERISK-26667) Segfault in res_sorcery_memory_cache

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-26667:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Segfault in res_sorcery_memory_cache
> ------------------------------------
>
>                 Key: ASTERISK-26667
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26667
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_sorcery_memory_cache
>    Affects Versions: 13.12.2
>         Environment: Ubuntu 16.04.1 Kernel 4.4.0-53
>            Reporter: Jesse Ross
>            Severity: Critical
>
> Asterisk crashes 2-3 times a day with this outputted to /var/log/syslog: 
> Dec 20 12:45:00 voip kernel: [618425.917499] asterisk[14173]: segfault at 0 ip 00000000005e0755 sp 00007fc6aafb6cc0 error 4 in asterisk[400000+2ca000]
> No calls were happening. 4 devices were registered to Asterisk.



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