[asterisk-bugs] [JIRA] (ASTERISK-22093) Deadlock due to locking inversion between PBX context lock and channel lock while reloading dialplan through pbx_lua
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Mon Jul 29 16:19:04 CDT 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-22093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rusty Newton updated ASTERISK-22093:
------------------------------------
Status: Waiting for Feedback (was: Open)
> Deadlock due to locking inversion between PBX context lock and channel lock while reloading dialplan through pbx_lua
> --------------------------------------------------------------------------------------------------------------------
>
> Key: ASTERISK-22093
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-22093
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/PBX, PBX/pbx_lua
> Affects Versions: 11.5.0
> Reporter: David Brillert
> Assignee: David Brillert
> Severity: Critical
> Attachments: 7_26_2013 gdb thread apply all bt full.txt, gdb thread apply all bt full.txt, gdb thread apply all bt.txt, valgrind.rar
>
>
> Third deadlock in two weeks.
> Asterisk not built with NOT_OPTIMIZED or thread debug options.
> The best I could do was attach GDB to Asterisk PID and get a thread apply all BT (attached)
--
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
More information about the asterisk-bugs
mailing list