[asterisk-bugs] [JIRA] (ASTERISK-22208) Extremely high CPU load and segfaults on a reload

[David Brillert (JIRA)]

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

David Brillert commented on ASTERISK-22208:
-------------------------------------------

If I look at the first few lines of the backtrace
#0  0x08116809 in ast_hashtab_start_traversal ()
(gdb) bt
#0  0x08116809 in ast_hashtab_start_traversal ()
#1  0x08161341 in ast_merge_contexts_and_delete ()
#2  0x00abda9c in pbx_load_module () at pbx_config.c:1855
#3  0x081210fa in ast_module_reload ()
#4  0x080c812e in handle_core_reload ()
#5  0x080c9949 in ast_cli_command_full ()

And I watch the reload the suspicious part is this:


[2013-07-26 13:12:26]     -- Registered extension context 'parkedcalls'; registrar: features
[2013-07-26 13:12:26]     -- merging incls/swits/igpats from old(parkedcalls) to new(parkedcalls) context, registrar = pbx_config
[2013-07-26 13:12:26]     -- Added extension '7000' priority 1 to parkedcalls
[2013-07-26 13:12:26]     -- merging incls/swits/igpats from old(parkedcalls_default) to new(parkedcalls_default) context, registrar = pbx_config
[2013-07-26 13:12:26] WARNING[1474]: pbx.c:9619 add_priority: Unable to register extension '7000' priority 1 in 'parkedcalls_default', already in use
[2013-07-26 13:12:26]     -- Dropping old dialplan item parkedcalls_default/7000/1 [Park()] (registrar=features) due to conflict with new dialplan
[2013-07-26 13:12:26]     -- merging incls/swits/igpats from old(parkedcalls_tenant) to new(parkedcalls_tenant) context, registrar = pbx_config
[2013-07-26 13:12:26] WARNING[1474]: pbx.c:9619 add_priority: Unable to register extension '7000' priority 1 in 'parkedcalls_tenant', already in use
[2013-07-26 13:12:26]     -- Dropping old dialplan item parkedcalls_tenant/7000/1 [Park()] (registrar=features) due to conflict with new dialplan

Attaching features.conf and a new valgrind trace during today's testing.

                
> Extremely high CPU load and segfaults on a reload
> -------------------------------------------------
>
>                 Key: ASTERISK-22208
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22208
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/General
>    Affects Versions: 11.5.0
>         Environment: CentOS 5.9 32 bit
>            Reporter: David Brillert
>            Severity: Critical
>         Attachments: 7_26_2013 gdb thread apply all bt full.txt, core 12843 segfault bt full.txt, core_31T09_gdb bt full.txt, core_show_locks.txt, lab_7_31_2013 gdb thread apply all bt full.txt, valgrind.rar
>
>
> CPU load in htop will register in the 60's and or 80's after a reload until I restart Asterisk.
> Ticket is open at the request of Rusty Newton in relationship to ASTERISK-22093

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