[asterisk-bugs] [JIRA] (ASTERISK-28209) Repeated SegFaults on 16.1.0; stable on 13.24.0

[Joshua C. Colp (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua C. Colp updated ASTERISK-28209:
--------------------------------------

    Assignee: Gregory Massel
      Status: Waiting for Feedback  (was: Triage)

This appears to be the result of faxing. We would need to see the configuration, console output, and SIP trace to see the interaction.

> Repeated SegFaults on 16.1.0; stable on 13.24.0
> -----------------------------------------------
>
>                 Key: ASTERISK-28209
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28209
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly.
>    Affects Versions: 16.1.0
>         Environment: Ubuntu 16.04 LTS, E3-1285, 32GB RAM
>            Reporter: Gregory Massel
>            Assignee: Gregory Massel
>         Attachments: core-dump-2018-12-13-08h04-brief.txt, core-dump-2018-12-13-08h04-full.txt, core-dump-2018-12-13-08h04-locks.txt, core-dump-2018-12-13-08h04-thread1.txt, core-dump-2018-12-13-08h42-brief.txt, core-dump-2018-12-13-08h42-full.txt, core-dump-2018-12-13-08h42-locks.txt, core-dump-2018-12-13-08h42-thread1.txt
>
>
> After upgrading to 16.1.0, Asterisk crashed six times in the space of an hour. After downgrading to 13.24.0, it has been rock solid for a number of days. Prior to that it was on 13.23.1 and rock solid for weeks.
> I cannot isolate which component is causing the issue, however, the one possible area in which this server is unique (versus another similar server that is running stable on 16.1.0) is that it uses res_odbc and func_odbc extensively. But blaming those components would be speculative.
> I have attached two backtraces from two different crash events.



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