Segfault with jemalloc 3.4.
Jason Evans
jasone at canonware.com
Thu Oct 3 14:11:49 PDT 2013
On Oct 1, 2013, at 5:56 AM, adnan akbar <chaudry.adnan.akbar at gmail.com> wrote:
> I have been using the jemalloc 3.4.0-0-g0ed518e5dab789ad2171bb38977a8927e2a26775. Usually it runs fine but i have a rare crash at the following location. And sometime while allocating. Any pointer regarding the resolution would be helpful.
>
> (gdb) bt
> #0 tcache_dalloc_small (ptr=0x7f1be585cc00)
> at include/jemalloc/internal/tcache.h:405
> #1 arena_dalloc (ptr=0x7f1be585cc00) at include/jemalloc/internal/arena.h:1003
> #2 idallocx (ptr=0x7f1be585cc00)
> at include/jemalloc/internal/jemalloc_internal.h:913
> #3 iqallocx (ptr=0x7f1be585cc00)
> at include/jemalloc/internal/jemalloc_internal.h:932
> #4 iqalloc (ptr=0x7f1be585cc00)
> at include/jemalloc/internal/jemalloc_internal.h:939
> #5 js_free (ptr=0x7f1be585cc00) at src/jemalloc.c:1272
> #6 0x00007f1c4af5180d in std::basic_string<char, std::char_traits<char>, mcommons::mem::JEAllocator<char> >::_Rep::_M_destroy(mcommons::mem::JEAllocator<char> const&) () from ../mcommons/output/libmcommons.so
> #7 0x00007f1c42dec17f in handlers::userhandlers::handleUserSessionEvent(mcommons::security::Session*, bool) () from ../LPConnector/output/libLPConnector.so
> #8 0x00007f1c4af9de93 in mcommons::framework::Consumer::processDescIO(unsigned long, unsigned long) const () from ../mcommons/output/libmcommons.so
> ---Type <return> to continue, or q <return> to quit---
> #9 0x00007f1c4af9e2ee in mcommons::framework::Consumer::run() ()
> from ../mcommons/output/libmcommons.so
> #10 0x00007f1c4af66389 in start_persistent_thread(void*) ()
> from ../mcommons/output/libmcommons.so
> #11 0x0000003bd7007851 in start_thread () from /lib64/libpthread.so.0
> #12 0x0000003bd64e890d in nfsservctl () from /lib64/libc.so.6
> #13 0x0000000000000000 in ?? ()
This backtrace may indicate that your application is double-freeing an allocation. The crash may occur long after the double-free occurs. In order to narrow down the problem, I recommend using a debug build of jemalloc and disabling tcache (either at compile time or at run time) so that assertions in the arena code catch the error immediately.
Jason
More information about the jemalloc-discuss
mailing list