Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-3703

Memory corruption likely related to page splitting

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • None
    • None
    • Storage 2017-11-13

    Description

      I noticed that http://build.wiredtiger.com:8080/job/wiredtiger-test-format-stress-zseries/35392/
      is hung and has been running for 16 hours. Running pmp shows:

            4 ??,__wt_sleep,__wt_ref_state_yield_sleep,__wt_page_in_func,__wt_page_swap_func,__wt_row_search,__cursor_row_search,__btcur_update,__wt_btcur_update,__curfile_update,row_update,ops,start_thread,thread_start
            4 __lll_lock_wait_private,__lll_lock,_int_free,__GI___libc_free,__wt_free_int,__wt_free_update_list,__free_update,__free_page_modify,__page_out_int,__wt_ref_out_int,__wt_split_rewrite,__evict_page_dirty_update,__wt_evict,__evict_page,__evict_lru_pages,__wt_evict_thread_run,__thread_run,start_thread,thread_start
            2 
            1 ??,__wt_sleep,__wt_ref_state_yield_sleep,__wt_page_in_func,__wt_page_swap_func,__wt_row_search,__cursor_row_search,__wt_btcur_search,__wt_btcur_modify,__curfile_modify,row_modify,ops,start_thread,thread_start
            1 __pthread_cond_timedwait,__wt_cond_wait_signal,__wt_cond_wait,__sweep_server,start_thread,thread_start
            1 __pthread_cond_timedwait,__wt_cond_wait_signal,__wt_cond_wait,__evict_pass,__evict_server,__wt_evict_thread_run,__thread_run,start_thread,thread_start
            1 __lll_lock_wait_private,__lll_lock,__GI___libc_malloc,_dl_map_object_deps,dl_open_worker,_dl_catch_error,_dl_open,do_dlopen,_dl_catch_error,dlerror_run,__GI___libc_dlopen_mode,init,__GI___pthread_once,__GI___backtrace,catch_segfault,<signal,malloc_consolidate,_int_malloc,__libc_calloc,__wt_calloc,__wt_row_modify,__cursor_row_modify_v,__btcur_update,__wt_btcur_modify,__curfile_modify,row_modify,ops,start_thread,thread_start
            1 __GI___pthread_once,__GI___backtrace,catch_segfault,<signal,__GI_raise,__GI_abort,wts_ops,main
      

      This is running changeset 4ff5d172ed42bbc703bc8d80d6f5642acbe7d777 which is the tip of develop before the merge/revert of WT-3652. So it should be the same as the current tip of develop theoretically.

      Attachments

        Issue Links

          Activity

            People

              alexander.gorrod@mongodb.com Alexander Gorrod
              sue.loverso@mongodb.com Susan LoVerso
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: