Segfault from recent LSM changes

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None

      The changes in WT-3012 are causing most LSM runs of test/format to segv with this stack:

      /c/jenkins/jenkins/workspace/wiredtiger-test-format-stress/build_posix/../src/include/btree.i:37(__wt_page_is_modified)[0x51a510]
/c/jenkins/jenkins/workspace/wiredtiger-test-format-stress/build_posix/../src/include/btree.i:1578(__wt_btree_lsm_switch_primary)[0x51a5ed]
/c/jenkins/jenkins/workspace/wiredtiger-test-format-stress/build_posix/../src/lsm/lsm_work_unit.c:387(__wt_lsm_checkpoint_chunk)[0x51bd8f]
/c/jenkins/jenkins/workspace/wiredtiger-test-format-stress/build_posix/../src/lsm/lsm_worker.c:64 (discriminator 3)(__lsm_worker_general_op)[0x443410]

              Assignee:
              David Hows (Inactive)
              Reporter:
              Susan LoVerso (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: