[OpenSIPS-Devel] [ opensips-Bugs-3610016 ] Memory Leak RabbitMQ

SourceForge.net noreply at sourceforge.net
Tue Apr 9 22:16:42 CEST 2013


Bugs item #3610016, was opened at 2013-04-04 06:56
Message generated for change (Comment added) made by digipigeon
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3610016&group_id=232389

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: 1.9.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Digipigeon (digipigeon)
Assigned to: Razvan Crainea (razvancrainea)
Summary: Memory Leak RabbitMQ

Initial Comment:
After upgrading from 1.8.2 to 1.9.x (latest), and also confirming the error on the trunk head. I am getting crashes of opensips:

CRITICAL:core:qm_free: freeing already freed pointer, first free: rabbitmq_send.c: rmq_process(323) - aborting
CRITICAL:core:qm_free: freeing already freed pointer, first free: dlg_profile.c: destroy_linkers(610) - aborting

BT FULL

#0  0x00007fac6d858425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1  0x00007fac6d85bb8b in abort () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#2  0x0000000000503425 in qm_free (qm=<optimised out>, p=0x7fac0be20d80, file=<optimised out>, func=<optimised out>, line=<optimised out>) at mem/q_malloc.c:450
        f = <optimised out>
        size = <optimised out>
        __FUNCTION__ = "qm_free"
#3  0x00007fac63049bb7 in rmq_process (rank=<optimised out>) at rabbitmq_send.c:323
        __FUNCTION__ = "rmq_process"
#4  0x00000000004b585d in start_module_procs () at sr_module.c:585
        m = 0x7fac6985a850
        n = <optimised out>
        l = <optimised out>
        x = <optimised out>
        __FUNCTION__ = "start_module_procs"
#5  0x0000000000414edc in main_loop () at main.c:818
        i = <optimised out>
        pid = <optimised out>
        si = <optimised out>
        startup_done = 0x0
        chd_rank = 0
        rc = <optimised out>
        load_p = 0x0
#6  main (argc=<optimised out>, argv=<optimised out>) at main.c:1557
        cfg_log_stderr = <optimised out>
        cfg_stream = <optimised out>
        c = <optimised out>
        r = <optimised out>
        tmp = 0x7fff847dcf81 ""
        tmp_len = <optimised out>
        port = <optimised out>
        proto = <optimised out>
        options = 0x5843d0 "f:cCm:M:b:l:n:N:rRvdDETSVhw:t:u:g:P:G:W:o:"
        ret = -1
        seed = 2612855874
        rfd = -496847072
        __FUNCTION__ = "main"


I believe that the problem is related to rabbitmq module, as it does not appear to crash when I don't use enable the module

----------------------------------------------------------------------

>Comment By: Digipigeon (digipigeon)
Date: 2013-04-09 13:16

Message:
Hello,

Unfortunately this did not solve the issue, it crashed again:

last informative log line:

CRITICAL:core:qm_free: freeing already freed pointer, first free:
rabbitmq_send.c: rmq_process(323) - aborting

BT FULL:

(gdb) bt full
#0  0x00007f770cdc5425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1  0x00007f770cdc8b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#2  0x0000000000503425 in qm_free (qm=<optimised out>, p=0x7f76aaf1a990,
file=<optimised out>, func=<optimised out>, line=<optimised out>) at
mem/q_malloc.c:450
        f = <optimised out>
        size = <optimised out>
        __FUNCTION__ = "qm_free"
#3  0x00007f77025b7597 in rmq_process (rank=<optimised out>) at
rabbitmq_send.c:323
        __FUNCTION__ = "rmq_process"
#4  0x00000000004b585d in start_module_procs () at sr_module.c:585
        m = 0x7f7708dc7850
        n = <optimised out>
        l = <optimised out>
        x = <optimised out>
        __FUNCTION__ = "start_module_procs"
#5  0x0000000000414edc in main_loop () at main.c:818
        i = <optimised out>
        pid = <optimised out>
        si = <optimised out>
        startup_done = 0x0
        chd_rank = 0
        rc = <optimised out>
        load_p = 0x0
#6  main (argc=<optimised out>, argv=<optimised out>) at main.c:1557
        cfg_log_stderr = <optimised out>
        cfg_stream = <optimised out>
        c = <optimised out>
        r = <optimised out>
        tmp = 0x7fff64ee8f81 ""
        tmp_len = <optimised out>
        port = <optimised out>
        proto = <optimised out>
        options = 0x5843d0 "f:cCm:M:b:l:n:N:rRvdDETSVhw:t:u:g:P:G:W:o:"
        ret = -1
        seed = 129474967
        rfd = -2118547680
        __FUNCTION__ = "main"

Regards Jonathan


----------------------------------------------------------------------

Comment By: Razvan Crainea (razvancrainea)
Date: 2013-04-09 09:07

Message:
Hi, Jonathan!

I have found a small bug in the rabbitmq module. I have attached a patch
here, can you please run it and see if this fixes your bug?

Best regards,
Răzvan

----------------------------------------------------------------------

Comment By: Digipigeon (digipigeon)
Date: 2013-04-08 13:01

Message:
I can confirm 4 full days of uptime without rabbitmq module enabled.
No Crashes, 99% sure that is the cause of it.

----------------------------------------------------------------------

Comment By: Digipigeon (digipigeon)
Date: 2013-04-04 07:28

Message:
Hi, 

The problem does not happen at start-up.
I haven't noticed any other errors apart from what I have wrote.
Those two messages were from the same run, they were output just before
opensips crashed.
At present I am 2 hours into running ver 1.9 (excluding rabbitmq), without
any crashes or error messages. Previously the crash happened within the
first 15 minutes, so I believe that it is stable, but I will update if this
instance crashes.

Regards Jonathan

----------------------------------------------------------------------

Comment By: Razvan Crainea (razvancrainea)
Date: 2013-04-04 07:21

Message:
Hi!

Does this happen at startup or later, at runtime? Do you see any errors
before opensips displays the Critical warning? Also, can you confirm that
the two Critical messages are from different runs. Finally, please confirm
that after removing the rabbitmq  you are able to run your platform
normally.

Best regards,
Răzvan

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3610016&group_id=232389



More information about the Devel mailing list