Crash with jemalloc 2.2.1

[Felipe Wilhelms Damasio - Taghos]

    Hi Again,

    I don't know if this helps, but here it is with "bt full":

#0  arena_avail_comp (arena=0x1000a80, size=36864, large=true, zero=true) at
src/arena.c:222
        b_size = 0
#1  arena_avail_tree_nsearch (arena=0x1000a80, size=36864, large=true,
zero=true) at src/arena.c:249
        cmp = 1
#2  arena_run_alloc (arena=0x1000a80, size=36864, large=true, zero=true) at
src/arena.c:593
        chunk = <value optimized out>
        run = <value optimized out>
        mapelm = 0x0
        key = {u = {rb_link = {rbn_left = 0x17, rbn_right_red = 0x1},
ql_link = {qre_next = 0x17, qre_prev = 0x1}}, bits = 36865}
#3  0x00007fe240427b20 in arena_malloc_large (arena=0x1000a80, size=36864,
zero=80) at src/arena.c:1474
        ret = <value optimized out>
#4  0x00007fe240422007 in icalloc (num=<value optimized out>, size=35472) at
include/jemalloc/internal/jemalloc_internal.h:620
No locals.
#5  calloc (num=<value optimized out>, size=35472) at src/jemalloc.c:1185
        ret = <value optimized out>
        num_size = 0
        usize = 36864
#6  0x0000000000408a76 in SES_new (fd=11191) at cache_session.c:11
        http = 0x4dac9495
        t = 0x100000001
#7  0x000000000041563e in main (argc=3, argv=0x7fff357085c8) at server.c:2261
        tmp = 0x59c96000
        opt = -1
        hints = {ai_flags = 1, ai_family = 0, ai_socktype = 1, ai_protocol =
0, ai_addrlen = 0, ai_addr = 0x0, ai_canonname = 0x0, ai_next = 0x0}
        res = 0x1410680
        r = 0x0
        b = 1
        a = 0x14106b0
        serv_sock = 5
        client_sock = 11191
        client_length = 16
        cont = 3
        serv_address = {sin_family = 2, sin_port = 56581, sin_addr = {s_addr
= 0}, sin_zero = "\000\000\000\000\000\000\000"}
        client_address = {sin_family = 2, sin_port = 57593, sin_addr =
{s_addr = 1363629243}, sin_zero = "\000\000\000\000\000\000\000"}
        timeout_session_thread = 140566642198288
        purge_backup_thread = 140566650590992
        i = 16
        tmp = 0x0
        sac = {__sigaction_handler = {sa_handler = 0x1, sa_sigaction = 0x1},
sa_mask = {__val = {0 <repeats 16 times>}}, sa_flags = 268435456,
          sa_restorer = 0}
        on = 1
        attr = {__size = '\000' <repeats 17 times>, "\020", '\000' <repeats
16 times>, "\b", '\000' <repeats 20 times>, __align = 0}
        WSPoolThreads = 0x7fff35708270


    Cheers,

--
Felipe Wilhelms Damasio


TAGHOS - Tecnologia

Rua Prof. Alvaro Alvim, 211

Porto Alegre - RS - (51) 3239-3180

www.taghos.com.br <http://www.taghos.com.br/>



Em 18/04/2011 17:11, Felipe Wilhelms Damasio - Taghos escreveu:
> Hi all,
>
> I'm using jemalloc to build a webcache system.
>
> I'm doing around 600-700 calloc/free per second. (a calloc-per-new-session).
>
> It's a linux machine with kernel 2.6.34 and glibc 2.11.2.
>
> jemalloc was compiled with:
>
>     ./configure  --enable-prof --enable-dss --enable-fill --enable-stats 
> --enable-xmalloc --enable-swap
>
> I have no malloc options file.
>
> At some point, my program crashed. I generated a core dump and a gdb bt
> showed this:
>
> #0  arena_avail_comp (arena=0x1000a80, size=36864, large=true, zero=true) at
> src/arena.c:222
> 222        size_t b_size = b->bits & ~PAGE_MASK;
> (gdb) bt
> #0  arena_avail_comp (arena=0x1000a80, size=36864, large=true, zero=true) at
> src/arena.c:222
> #1  arena_avail_tree_nsearch (arena=0x1000a80, size=36864, large=true,
> zero=true) at src/arena.c:249
> #2  arena_run_alloc (arena=0x1000a80, size=36864, large=true, zero=true) at
> src/arena.c:593
> #3  0x00007fe240427b20 in arena_malloc_large (arena=0x1000a80, size=36864,
> zero=80) at src/arena.c:1474
> #4  0x00007fe240422007 in icalloc (num=<value optimized out>, size=35472) at
> include/jemalloc/internal/jemalloc_internal.h:620
> #5  calloc (num=<value optimized out>, size=35472) at src/jemalloc.c:1185
> #6  0x0000000000408a76 in SES_new (fd=11191) at cache_session.c:11
> #7  0x000000000041563e in main (argc=3, argv=0x7fff357085c8) at server.c:2261
>
> Is this indication of a bug in jemalloc or in my program?
>
> What other info can I provide to help track this down?
>
> Thanks,
>