Bug #902
closedCrash on consumer daemon due to double free or corruption
0%
Description
We have observed crash on consumer daemon, during repetitive restarts of our trace generating system (target).
Crash is observed during the startup of the system. Reason for the crash is "double free or corruption (out)".
Below is the call trace from the core dump generated:
#0 0x000000804ce20000 in __GI_raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:55
#1 0x000000804ce25850 in __GI_abort () at abort.c:89
#2 0x000000804ce60e24 in __libc_message (do_abort=<optimized out>, fmt=<optimized out>) at ../sysdeps/posix/libc_fatal.c:175
#3 0x000000804ce6f368 in malloc_printerr (action=<optimized out>, str=0x804cf4f220 "double free or corruption (out)", ptr=<optimized out>) at malloc.c:4958
#4 0x000000804ce701bc in _int_free (av=<optimized out>, p=<optimized out>, have_lock=<optimized out>) at malloc.c:3829
#5 0x0000000010011ab8 in ?? ()
Currently we are using LTTng tools version 2.6.
Can you please let us know if you have observed any similar issue like above?
Updated by Jérémie Galarneau over 9 years ago
Can you launch the consumerd in verbose mode and append the logs to the bug report?
To do so, launch the session daemon manually with the --verbose-consumer option.
Updated by Jérémie Galarneau about 9 years ago
- Status changed from New to In Progress
- Assignee set to Mathieu Desnoyers
- Target version changed from 2.6 to 2.7
Updated by Jérémie Galarneau about 9 years ago
- Target version changed from 2.7 to 2.6
Updated by Jérémie Galarneau over 8 years ago
- Status changed from In Progress to Invalid
No activity for 8 months and not enough info to investigate. Closing.