[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)
noreply at issues.asterisk.org
Tue Nov 11 08:30:29 CST 2014
[ 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,
We had 2 more crashes on 2 different servers with similar core file.
Going over the code it seems to me that the problem is with line 3158 in sip_transaction.c:
PJ_ASSERT_RETURN(event->type == PJSIP_EVENT_TX_MSG &&
event->body.tx_msg.tdata == tsx->last_tx,
PJ_EINVALIDOP);
Probably the expression is false. The first part of it is fine - in the core file you can see that 'event->type == PJSIP_EVENT_TX_MSG'.
However, the second part I am not sure. Maybe because that transaction is completed 'tsx->last_tx' is no longer valid, or maybe the whole expression is incorrect.
It seems to very simple to fix - could you please look into it.
Thank you.
Yaron.
> 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_10_11_18_19.txt, backtrace_6_11_12_23.txt, backtrace.txt, config.log.lab, config.log.live, 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)
More information about the asterisk-bugs
mailing list