[asterisk-bugs] [JIRA] (ASTERISK-24471) Crash - assert_fail in libc in pjmedia_sdp_neg_negotiate from /usr/local/lib/libpjmedia.so.2

[yaron nahum (JIRA)]

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

yaron nahum updated ASTERISK-24471:
-----------------------------------

    Status: Waiting for Feedback  (was: Waiting for Feedback)

Hi Rusty,
I have recompiled both PJPROJECT and ASTERISK - with -g for PJPROJECT and on the menuselect I added DONT_OPTIMZE.
I did it on one of my live servers and on the lab server.
Meanwhile I prepared a SIPP script that just sends an INVITE to my lab system and disconnects the call with CANCEL just before the 200OK should be sent - in order to simulate the scenario I suspect that causes the issue. 
It took a while but then the ASTERISK crashed. I have attached the core file.
Meanwhile I am waiting for my live system to crash also - it might take a day or two.
Hope you find the issue.

> Crash - assert_fail in libc in pjmedia_sdp_neg_negotiate from /usr/local/lib/libpjmedia.so.2
> --------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24471
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24471
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip, Resources/res_pjsip
>    Affects Versions: 12.2.0, 12.6.1
>         Environment: centos 6
>            Reporter: yaron nahum
>            Assignee: yaron nahum
>            Severity: Critical
>         Attachments: backtrace_6_11_12_23.txt, backtrace.txt, yaron.debug.1
>
>
> We have had several crashes recent days on servers running 12.2.0rc1. We upgraded one of the servers to 12.6.1 and it crashed also. The crashes occur every couple of days per server.
> Our service uses AGI's for external logic. It also uses spandsp for fax receiving and sending.
> *** Yaron -
> Going over the debug messages I can see that the last call before the reboot was an incoming that was canceled in the same second of the initial INVITE. In between I can see that we activated a certain AGI, and then  after we got the cancel we jumped to h extension there we activated another AGI. 
> We are trying to simulated this scenario with SIPP and see if the reboot occurs. 
> One more thing I forgot to mention is that we have a lot of zombie processes running all the time related to Asterisk. It might be related to the reboot.



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