[asterisk-bugs] [JIRA] (ASTERISK-25251) getifaddrs() blocks infinitely in PJSIP
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Fri Nov 20 06:31:33 CST 2015
[ https://issues.asterisk.org/jira/browse/ASTERISK-25251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=228386#comment-228386 ]
Asterisk Team commented on ASTERISK-25251:
------------------------------------------
This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable.
> getifaddrs() blocks infinitely in PJSIP
> ---------------------------------------
>
> Key: ASTERISK-25251
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25251
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/res_pjsip
> Affects Versions: 13.1.1, 13.3.2, 13.4.0
> Environment: Fedora 22
> Reporter: Gergely Dömsödi
> Assignee: Rusty Newton
> Attachments: bt-nodns.txt, bt.txt, bt.txt, fd.txt, locks-nodns.txt, locks.txt, taskprocessors.txt, threads.txt
>
>
> Using PJSIP, after about 10-20 minutes of SIP traffic between two PJSIP peers, a deadlock occurs and Asterisk cannot serve SIP traffic anymore. Incoming INVITES can be seen with a tcpdump, but it is not even visible in pjsip log.
> The issue is reproducible with both the "vanilla" asterisk package in Fedora 22 (13.1.1), with the package currently in updates-testing (13.3.2), and a custom-built 13.4.0. Tried with PJSIP 2.3 from Fedora and a custom built 2.4, both were affected.
> When in the deadlock, PJSIP commands continue to work (pjsip show *), but asterisk cannot be stopped, core stop now just returns, but nothing happens. Only SIGKILL can pull out asterisk from this state.
> Attached outputs and backtraces are from the custom built 13.4.0, with PJSIP 2.4.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list