-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
None
-
None
The MongoDB test suite has started seeing occasional failures where there is a segfaut during wt_hs_insert_updates - we should find the root cause and fix it.
Stacktrace:
mongo::stack_trace_detail::(anonymous namespace)::printStackTraceImpl(mongo::stack_trace_detail::(anonymous namespace)::Options const&, mongo::StackTraceSink*) [clone .constprop.606]
mongo::printStackTrace()
mongo::(anonymous namespace)::abruptQuitWithAddrSignal(int, siginfo*, void*)
WasmFaultHandler(int, siginfo*, void*)
_L_unlock_16
__wt_hs_insert_updates
__rec_write_wrapup
__wt_reconcile
__wt_sync_file
__checkpoint_tree.constprop.13
__txn_checkpoint_wrapper
__wt_txn_checkpoint
__session_checkpoint.cold.49
mongo::WiredTigerSessionCache::waitUntilDurable(mongo::OperationContext*, mongo::WiredTigerSessionCache::Fsync, mongo::WiredTigerSessionCache::UseJournalListener)
mongo::WiredTigerKVEngine::flushAllFiles(mongo::OperationContext*, bool)
mongo::(anonymous namespace)::FSyncLockThread::run()
mongo::BackgroundJob::jobBody()
std::thread::_State_impl<std::thread::_Invoker<std::tuple<mongo::stdx::thread::thread<mongo::BackgroundJob::go()::{lambda()#2}, , 0>(mongo::BackgroundJob::go()::{lambda()#2})::{lambda()#1}> > >::_M_run()
execute_native_thread_routine
start_thread
clone
The failure first happened on 10th June - so we should start looking at changes that have been made this week which might cause the symptom.
- duplicates
-
-
- Closed
-