[asterisk-bugs] [JIRA] (ASTERISK-20552) Locked (channel.c): MUTEX 4845 ast_write chan

[Rusty Newton (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-20552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Newton updated ASTERISK-20552:
------------------------------------

    Status: Open  (was: Triage)
    
> Locked (channel.c): MUTEX 4845 ast_write chan 
> ----------------------------------------------
>
>                 Key: ASTERISK-20552
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20552
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: SVN
>         Environment: SVN-branch-1.8-r374802
>            Reporter: aragon
>            Assignee: Matt Jordan
>         Attachments: thread apply all bt.txt
>
>
> First a bunch of these queue_frame warnings and then I checked core show locks and attached gdb.
> GDB debug info attached.
> [2012-10-10 21:09:19] WARNING[22800]: channel.c:1507 __ast_queue_frame: Exceptionally long voice queue length queuing to Local/6147 at default-agent-00000006;1
> [2012-10-10 21:09:19] WARNING[22800]: channel.c:1507 __ast_queue_frame: Exceptionally long voice queue length queuing to Local/6147 at default-agent-00000006;1
> [2012-10-10 21:09:19] WARNING[22873]: channel.c:1507 __ast_queue_frame: Exceptionally long voice queue length queuing to Local/6120 at default-agent-0000001d;2
> 6000*CLI> core show locks
> =======================================================================
> === Currently Held Locks ==============================================
> =======================================================================
> ===
> === <pending> <lock#> (<file>): <lock type> <line num> <function> <lock name> <lock addr> (times locked)
> ===
> === Thread ID: 0x41387940 (pbx_thread           started at [ 5374] pbx.c ast_pbx_start())
> === ---> Lock #0 (channel.c): MUTEX 4845 ast_write chan 0x1fd3c4c0 (1)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira