wtperf failure: accessing a freed page

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • WT1.6.5
    • Affects Version/s: None
    • Component/s: None
    • None
    • None

      I'm running a script over the wtperf configs and the 3rd iteration of evict-lsm took a segv.

      (gdb) bt
#0  0x00000000004432c5 in __wt_tree_walk (session=0xd17060, 
    pagep=0x7fb9401c3358, flags=16) at ../src/btree/bt_walk.c:242
WT-1  0x0000000000431ff6 in __evict_walk_file (session=0xd17060, 
    slotp=0x7fb9f041bd5c, clean=1) at ../src/btree/bt_evict.c:826
WT-2  0x0000000000431ac5 in __evict_walk (session=0xd17060, 
    entriesp=0x7fb9f041bdc0, clean=1) at ../src/btree/bt_evict.c:750
WT-3  0x00000000004316a6 in __evict_lru (session=0xd17060, clean=1)
    at ../src/btree/bt_evict.c:631
WT-4  0x0000000000430bb3 in __evict_worker (session=0xd17060)
    at ../src/btree/bt_evict.c:252
WT-5  0x00000000004307cc in __wt_cache_evict_server (arg=0xd17060)
    at ../src/btree/bt_evict.c:160
WT-6  0x00007fb9f10e4c6b in start_thread () from /lib64/libpthread.so.0
WT-7  0x00007fb9f0a1d5ed in clone () from /lib64/libc.so.6

241                     if ((prev && slot == 0) ||
242                         (!prev && slot == page->entries - 1)) {

(gdb) p *page
Cannot access memory at address 0x7f9239e9e4819bd6

      Not sure how reproducible it is, but clearly doesn't happen every time since the other 2 iterations passed.

            Assignee:
            Michael Cahill (Inactive)
            Reporter:
            Susan LoVerso (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: