[asterisk-bugs] [JIRA] (ASTERISK-25275) A11 SIGSEGV from pjnpath check_cached_response (ast_rtcp_read -> pj_stun_session_on_rx_pkt)

[Dade Brandon (JIRA)]

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

Dade Brandon updated ASTERISK-25275:
------------------------------------

    Attachment: commit log.txt

@Rusty Here is the top chunk of my commit log;  I forget which github repo I'm using which is a clone of svn, I'd be happy to pull in some additional data but there's a few changes that've gone in to 11 that I'm unhappy with and haven't been able to submit a bug report about yet, such as the change to ast_websocket_write that assumes a failure on the second write should close, rather than instead changing it to just a single write... which does make a difference in production...

It's a bit older than I thought, it looks like we diverged on 11.18.0-rc1
(Restricted to JIRA Users group)
> A11 SIGSEGV from pjnpath check_cached_response (ast_rtcp_read -> pj_stun_session_on_rx_pkt)
> -------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-25275
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25275
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 11.18.0
>         Environment: Ubuntu 14.04.2; Linux 3.13.0-24-generic SMP; Intel E3-1231 
> Openssl 1.0.1f-1ubuntu2.15 (Jun 11 2015; most recent available) 
> libsrtp0 / libsrtp0-dev 1.4.5~20130609~dfsg-1
>            Reporter: Dade Brandon
>         Attachments: 6-2-phx-crash_jul_22_1043am_backtrace.txt, 6-2-phx-crash_jul_22_1043am.p.txt.gz, atlas-backtrace-july22 2015.txt, commit log.txt
>
>
> This may be a duplicate of my other just-created issue, ASTERISK-25274, however since the backtrace has a different signal point, I am following previous instruction to create separate issues.
> We have the patch from ASTERISK-25103 added to trunk 11 with a few custom patches (mostly just debug messages). The following crash occurs infrequently (1-5 times per week, usually batched together and on the same server(s); based on the pattern I imagine that there is a remote factor in whether or not the crash occurs, such as a slow peer )
> A full backtrace and debug log will be attached shortly after this issue is created;  here is a snip of the top chunk of the backtrace, for assistance in reviewing the issue:
> {noformat}
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 check_cached_response
> #1 pj_stun_session_on_rx_pkt ()
> #2 pj_ice_sess_on_rx_pkt ()
> #3 __rtp_recvfrom
>  (instance=0xvalidptr, buf=0xvalidptr, size=8192, flags=0, sa=validptr, rtcp=1)
> {noformat}



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