[asterisk-bugs] [JIRA] (ASTERISK-24875) Randomly get segfaults processing WEBRTC calls

[Jacques Brooks (JIRA)]

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

Jacques Brooks updated ASTERISK-24875:
--------------------------------------

    Attachment: asterisklog.gz
                backtrace2.txt
                sip.conf

I've attached a backtrace, sip.conf and log file. As I alluded to before I'm assuming that the "bad magic" errors indicate that the problem has started to kick in so I've only included the log starting from 10 minutes before the "bad magic" errors kicked in. This time around didn't get the same segfault error but a general protection error - kernel: asterisk[536] general protection ip:7f23f2d97435 sp:7f22eae8a9a8 error:0 in libc-2.12.so[7f23f2c6c000+18a000].  The pjsip modules were not in the modules.conf files so I expected not to see any messages pertaining to pjsip but as you can see in the logs there definitely are pjsip messages; I'm hoping it's not an issue in terms of troubleshooting. You had also requested the pjsip.conf that we used when we tested with pjsip but I haven't attached since the box we tested with got corrupted and the pjsip.conf was lost so would have had to start from scratch for that.

> Randomly get segfaults processing WEBRTC calls
> ----------------------------------------------
>
>                 Key: ASTERISK-24875
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24875
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 11.16.0, 13.2.0
>         Environment: CentOS Linux
>            Reporter: Jacques Brooks
>            Assignee: Jacques Brooks
>            Severity: Critical
>         Attachments: asterisklog.gz, backtrace2.txt, backtrace.txt, sip.conf
>
>
> Asterisk randomly crashes when processing WEBRTC calls. Doesn't seem to be dependent on number of calls currently handling or how long Asterisk is running; have crashed with less than 10 calls and over 200 calls and have crashed with Asterisk running less than 20 minutes and at times when it's been running for hours  Using version 13.2 with sip.conf.  Tried to convert to pjsip.conf but was not very successful (would get only one or two calls up before crashing) so reverted back to sip.conf. 



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