Support Center > Search Results > SecureKnowledge Details
RouteD daemon might crash due to memory leak when PIM Sparse Mode multicast is configured
Symptoms
  • Output of "top" command / "ps auxw" command shows that memory consumption by RouteD daemon increases constantly.

    Example from "top" command:
    VIRT memory reached 3643m
    RES memory reached 3.3g
    SHR memory reached 8264
    %MEM reached 57
    
  • Fail-over in cluster due to Critical Device routed.

  • After enabling generation of core dump files per sk92764, core dump files for 'routed' process might be generated in the /var/log/dump/usermode/ directory.

  • RouteD core dump files contain the following function stack:

    #3  0x... in task_quit (code=12) at task/task_init.c
    #4  0x... in task_block_sbrk (size=4096) at task/task_block.c
    #5  0x... in task_page_alloc () at task/task_block.c
    #6  0x... in task_block__alloc (tbp=0x...) at task/task_block.c
    #7  0x... in sockdup (src=0x...) at net/sockaddr.c
    #8  0x... in pim_sm_find_active_rp (instp=0x..., group=0x..., masklen=...) at pim/pim_sm_rp.c
    #9  0x... in pim_sm_io_send_register (packet=0x... "E") at pim/pim_sm_reg.c
    #10 0x... in igmp_process_whole_pkt (buf=0x... "E") at igmp/igmp_util.c
    #11 0x... in igmp_process_kernel_call (igmp_recv_buf=0x... "E") at igmp/igmp_util.c
    #12 0x... in igmp_recv (tp=0x...) at igmp/igmp_util.c
    #13 0x... in task_process_sockets (...) at task/task_socket.c
    #14 0x... in main (a...) at task/task_init.c
    
Cause

Memory leak in RouteD daemon when PIM Sparse Mode multicast is configured.

Memory leak can be significant when the Security Gateway is mis-configured causing all multicast traffic to be encapsulated within PIM Register packets permanently.


Solution
Note: To view this solution you need to Sign In .