[asterisk-bugs] [JIRA] (ASTERISK-26969) Deadlock - chan_pjsip

Ross Beer (JIRA) noreply at issues.asterisk.org
Mon May 8 09:14:58 CDT 2017


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

Ross Beer edited comment on ASTERISK-26969 at 5/8/17 9:13 AM:
--------------------------------------------------------------

Further backtrace attached:

{noformat}
#0  0x00007f8cc531e353 in pj_lock_acquire (lock=0x626f3b303230) at ../src/pj/lock.c:180
180	    return (*lock->acquire)(lock->lock_object);
{noformat}


was (Author: rossbeer):
Further backtrace attached:

{noformat}
#0  0x00007f8cc531e353 in pj_lock_acquire (lock=0x626f3b303230) at ../src/pj/lock.c:180
{noformat}

> Deadlock - chan_pjsip
> ---------------------
>
>                 Key: ASTERISK-26969
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26969
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: GIT
>         Environment: Fedora 23
>            Reporter: Ross Beer
>            Assignee: Unassigned
>         Attachments: 05_backtrace-threads_2017-05-25_clean.txt, 07_backtrace-threads_2017-04-27_clean.txt, backtrace_20170508_clean.txt
>
>
> A deadlock has been introduced between the versions: 
> Asterisk GIT-13-13.15.0-rc1-64-ge851412M
> Asterisk GIT-13-13.15.0-rc1-80-g299376cM
> This is happening over multiple instances. 
> I am currently unable to run DEBUG_THREADS to identify, however I have backtraces when the system locks.
> This is running with the revert commit: 3e7c396a51b240088c475dd53e7bac9869376129 (bridging:  Ensure successful T.38 negotation)



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



More information about the asterisk-bugs mailing list