[asterisk-bugs] [JIRA] (ASTERISK-26853) res_rtp_asterisk: Crash in pjnath when receiving packet

Richard Mudgett (JIRA) noreply at issues.asterisk.org
Tue Mar 28 13:06:11 CDT 2017


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

Richard Mudgett commented on ASTERISK-26853:
--------------------------------------------

The logs aren't showing enough information to determine what is going on to identify a deadlock with the patch.  The classic deadlock can be shown by the CLI "core show locks" output as described by [1] with the menuselect compilation flags DONT_OPTIMIZE, DEBUG_THREADS, and BETTER_BACKTRACES enabled.  Along with that output a gcb backtrace [2] is also useful to determine what is going on for a deadlock.

By the way, to which version of Asterisk did you apply the patch?

[1] https://wiki.asterisk.org/wiki/display/AST/CLI+commands+useful+for+debugging
[2] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

> res_rtp_asterisk: Crash in pjnath when receiving packet
> -------------------------------------------------------
>
>                 Key: ASTERISK-26853
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26853
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_rtp_asterisk
>    Affects Versions: 13.14.0, 14.2.0
>         Environment: Debian jessie
>            Reporter: Studio ADAGIO
>            Assignee: Richard Mudgett
>         Attachments: backtrace.txt, Config.tar.gz, debug_deadlock.zip, debug.txt, gdb.txt, messages_deadlock, messages.log, valgrind.txt, verbose_deadlock, verbose.log
>
>
> Hi
> We have a business application that uses both conventional telephony and VoIP.
> We use the PJSIP library to make VoIP calls from mobile devices (Android & iOS). On server side we have Asterisk with PJSIP.
> Sometimes "Asterisk" process crash with "double free or corruption". This happens shortly after the INVITE transaction was finished (we hear about 0.5s of sound) and only if the call was started on Android device.
> We tried to reproduce the crash with other softphones (Zoiper, CSipSimple, Ekiga) and pjsua in CLI but it doesn't crash. Also it doesn't crash when iOS app is used. So, it seems that, the problem is with our Android implementation, but we don't know where to search for the solution.
> We tried workarounds from here: ASTERISK-25274
> ASTERISK-25275
> But nothing worked.
> This crash occur once in about 200 calls.
> After using Valgrind (valgrind.org) to analyze Asterisk memory, we restart Asterisk and crash is happening more often. Is there a link ?
> You will find backtrace and debug in attachments.
> We tried Asterisk versions: 13.14 and 14.2
> PJSSIP versions: 2.5.5, 2.6
> (We tried to change audio codec but nothing changed)
> Thanks a lot



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



More information about the asterisk-bugs mailing list