[asterisk-bugs] [JIRA] (ASTERISK-26669) PJSIP Segfault 13.13.1 (Bundled PJSIP)

[Nic Colledge (JIRA)]

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

Nic Colledge commented on ASTERISK-26669:
-----------------------------------------

Hi Richard,

Thanks for your reply. I applied the additional patch and ran through the distclean steps for pjsip. Ill report back with more traces etc. when it happens again.

It should just be IPv4 for provider DNS lookups.

Not sure if its important but one provider has both A and SRV records (_sip._udp.provideraddr.com). The other providers only have A records.
No AAAA (IPv6) addresses are returned for DNS lookups to the provider addresses. All were checked using dig on the box having the issues.

Thanks,
Nic.

> PJSIP Segfault 13.13.1 (Bundled PJSIP)
> --------------------------------------
>
>                 Key: ASTERISK-26669
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26669
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 13.13.1
>         Environment: Ubuntu 16.04.1 LTS, Linux 4.4.0-53-generic
>            Reporter: Nic Colledge
>            Assignee: Richard Mudgett
>         Attachments: backtrace-1482444465.txt, backtrace-1482482153.txt, backtrace-1482483920.txt, backtrace-1482496599.txt, backtrace-1482497243.txt, backtrace-1482498503.txt, backtrace.30388.ast3.1486008781-0413.txt, backtrace.30588.ast3.1486010460-0441.txt, backtrace.30719.ast3.1486015498-0604.txt, backtrace.36281.ast3.1486130000-1353.txt, backtrace.36368.ast3.1486140553-1649.txt, debug_log_0413.txt, debug_log_0441.txt, debug_log_0604.txt, debug_log_1353.txt, debug_log_1649.txt, jira_asterisk_26669_v13_test.patch
>
>
> Hi guys,
> Been getting an intermittent segfault with asterisk 13.13.1 since we upgraded. Its a low-load server but happens maybe a few times a day. 
> We jumped a few versions from 13.10 so not sure if this is a last-release regression or not.
> We have another higher-load server (with the same setup) that has not yet crashed in the same way.
> I will attach backtraces; the fault its self comes from pj_atomic_dec_and_get from /usr/lib/libasteriskpj.so



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