[asterisk-bugs] [JIRA] (ASTERISK-22857) Deadlock: Locked Here: chan_iax2.c line 9756 (socket_read)

[David Brillert (JIRA)]

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

David Brillert commented on ASTERISK-22857:
-------------------------------------------

Ideally I'd like to run with DEBUG_THREADS enabled, at least that way when I run into a deadlock I can get a trace right away.
But to answer your question no.  I do not normally run with DEBUG_THREADS.
                
> Deadlock: Locked Here: chan_iax2.c line 9756 (socket_read)
> ----------------------------------------------------------
>
>                 Key: ASTERISK-22857
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22857
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: SVN, 11.6.0
>         Environment: 64 bit CentOS, 4GB RAM
>            Reporter: David Brillert
>            Assignee: David Brillert
>            Severity: Critical
>         Attachments: backtrace.txt, core show locks_gdb thread apply all bt full.txt, core show locks svn manual.txt, gdbcorebtbtfull.txt, iax2 debug.txt, valgrind.txt
>
>
> Full deadlock no call processing, no SIP traffic.
> GDB output DONT_OPTIMIZE DEBUG_THREADS BETTER_BACKTRACES thread apply all bt full.txt attached.  The deadlock occurred overnight while the system was idle.
> It is happening on multiple production servers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira