[asterisk-bugs] [JIRA] (ASTERISK-22093) Deadlock due to locking inversion between PBX context lock and channel lock while reloading dialplan through pbx_lua

[David Brillert (JIRA)]

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

David Brillert commented on ASTERISK-22093:
-------------------------------------------

I have downloaded the customer's config to a lab server and starting valgrind.
It's taking a long time to start under Valgrind ;)

To confirm, after noloading pbx_lua you don't get a full deadlock, but CPU usage spikes.
- So far so good on the full deadlock

How long does the CPU usage hit the roof for?
- a long time, until I restart Asterisk

The trace = gdb thread apply all bt full.txt
    22/Jul/13 3:37 PM
Is a gdb attachment during a full deadlock with lua loaded.


The trace =  7_26_2013 gdb thread apply all bt full.txt
    26/Jul/13 10:56 AM
Is a gdb attachment during the high CPU load with noload => pbx_lua.so

                
> 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
>
>
> 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