Voxer 10k crash

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • WT2.4.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None

      The voxer-10k Jenkins job crashed with a seg fault early today. The stack is:

      #0  0x00000000004235aa in __wt_cond_signal ()
WT-1  0x000000000041ba20 in __wt_lsm_manager_push_entry ()
WT-2  0x0000000000478bc2 in __clsm_enter_update ()
WT-3  0x000000000047aafe in __clsm_update ()
WT-4  0x000000000040956a in worker ()
WT-5  0x00007f08770b7ddb in start_thread (arg=0x7f0856bf5700) at pthread_create.c:301
WT-6  0x00007f0876c00a1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

      This one is hard to reproduce because it is due to scheduling.

      The reason for the crash is that the condition does not exist. Looking at all the threads, the LSM manager thread and LSM worker threads have not started yet.

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

              Created:
              Updated:
              Resolved: