<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Oct 2, 2014, at 1:40 AM, Roel Van de Paar <<a href="mailto:roel.vandepaar@percona.com">roel.vandepaar@percona.com</a>> wrote:<div><blockquote type="cite"><div dir="ltr">Hi jemalloc list,<div><br></div><div>On Sep 11 I submitted this bug report, but have not seen any updates on it - any progress?</div></div></blockquote><div><br></div><div>This looks suspiciously like a crash due to the application performing a double free or write after free, but there's not enough information here to know for sure. You may be able to narrow the problem down by using a debug build, disabling tcache, etc. Please let us know if you determine that it is in fact a jemalloc bug.</div><div><br></div><div>Thanks,</div><div>Jason</div><br><blockquote type="cite"><div class="gmail_extra"><div class="gmail_quote">On Thu, Sep 11, 2014 at 8:13 AM, Roel Van de Paar <span dir="ltr"><<a href="mailto:roel.vandepaar@percona.com" target="_blank">roel.vandepaar@percona.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; position: static; z-index: auto;"><div dir="ltr"><div>Stack (as generated by mysqld):</div><div><br></div><div>Thread 20 (LWP 698):</div><div>+bt</div><div>#0 0x0000000005072771 in pthread_kill () from /lib64/libpthread.so.0</div><div>#1 0x0000000000ad3e5e in my_write_core (sig=11) at /mnt/workspace/percona-server-5.6-binaries-valgrind-yassl/label_exp/centos6-64/percona-server-5.6.20-68.0/mysys/stacktrace.c:422</div><div>#2 0x000000000073156f in handle_fatal_signal (sig=11) at /mnt/workspace/percona-server-5.6-binaries-valgrind-yassl/label_exp/centos6-64/percona-server-5.6.20-68.0/sql/signal_handler.cc:236</div><div>#3 <signal handler called></div><div>#4 0x0000000004e3ff98 in je_arena_dalloc_bin_locked () from /usr/lib64/libjemalloc.so.1</div><div>#5 0x0000000004e58881 in je_tcache_bin_flush_small () from /usr/lib64/libjemalloc.so.1</div><div>#6 0x0000000004e58fae in je_tcache_destroy () from /usr/lib64/libjemalloc.so.1</div><div>#7 0x0000000004e59183 in je_tcache_thread_cleanup () from /usr/lib64/libjemalloc.so.1</div><div>#8 0x000000000506dbf2 in __nptl_deallocate_tsd () from /lib64/libpthread.so.0</div><div>#9 0x000000000506de01 in start_thread () from /lib64/libpthread.so.0</div><div>#10 0x00000000063dc3dd in clone () from /lib64/libc.so.6</div><div><br></div><div>OS: Centos 7</div><div><br></div><div>jemalloc version: jemalloc.x86_64 0:3.6.0-1.el7 (libjemalloc.so.1 & libpthread.so[.0] attached</div><div><br></div><div>I have also attached a "bundle" of files which we usually attached to mysqld bug reports. </div><div>It contains a lot of mysqld-related information, like the core dump, stack traces generated etc.). </div><div>You never know, it may come in handy when researching this bug.</div><div><br></div><div>If you are interested in debug stack traces, please do sent me a compiled debug lib that I can use directly and I'll try to get (gdb) bt full stacks if I can repeat the issue.</div><div><br></div><div>Hope you can fix this. Thanks!</div></div></blockquote></div></div></blockquote></div><br></body></html>