[SERVER-16924] Access violation in Mongod (Insert only workload) Created: 17/Jan/15  Updated: 23/Feb/15  Resolved: 23/Feb/15

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 2.8.0-rc5
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Eitan Klein Assignee: Ramon Fernandez Marina
Resolution: Cannot Reproduce Votes: 0
Labels: 28qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-16918 Access violation in WT during insert ... Closed
Operating System: ALL
Steps To Reproduce:

2 replica set member
OS: Windows
workload: hammer.mongo
profile: insert only 100 threads

Participants:

 Description   

Dump file located (eitan6 Ip 10.4.111.166)
net use
eitan6 /u:administrator Admin01

\\eitan6\tmp\av.dmp
0:014> g
(5d84.5d94): Access violation - code c0000005 (!!! second chance !!!)
mongod!index_collator_extension+0x3b1566:
00007ff7`f2249776 4c3909          cmp     qword ptr [rcx],r9 ds:000000d8`7652efd0=????????????????
0:014> k
Child-SP          RetAddr           Call Site
000000d3`8e4deff0 00007ff7`f2234569 mongod!index_collator_extension+0x3b1566
000000d3`8e4df070 00007ff7`f225e7db mongod!index_collator_extension+0x39c359
000000d3`8e4df0c0 00007ff7`f1e9e4ba mongod!index_collator_extension+0x3c65cb
000000d3`8e4df0f0 00007ff7`f1e9fe35 mongod!index_collator_extension+0x62aa
000000d3`8e4df290 00007ff7`f1b4021b mongod!index_collator_extension+0x7c25
000000d3`8e4df3e0 00007ff7`f1b40f37 mongod!mongo::parseNumberFromStringWithBase<unsigned __int64>+0xb7b9b
000000d3`8e4df460 00007ff7`f1db93ba mongod!mongo::parseNumberFromStringWithBase<unsigned __int64>+0xb88b7
000000d3`8e4df560 00007ff7`f1e0384e mongod!mongo::parseNumberFromStringWithBase<unsigned __int64>+0x330d3a
000000d3`8e4df740 00007ff7`f1e04c0a mongod!mongo::parseNumberFromStringWithBase<unsigned __int64>+0x37b1ce
000000d3`8e4df7e0 00007ff7`f1e05244 mongod!mongo::parseNumberFromStringWithBase<unsigned __int64>+0x37c58a
000000d3`8e4df980 00007ff7`f1dfed1c mongod!mongo::parseNumberFromStringWithBase<unsigned __int64>+0x37cbc4
000000d3`8e4dfaf0 00007ff7`f1feba91 mongod!mongo::parseNumberFromStringWithBase<unsigned __int64>+0x37669c
000000d3`8e4dfd50 00007ff7`f22ef347 mongod!index_collator_extension+0x153881
000000d3`8e4dfd90 00007ff7`f22ef4ee mongod!index_collator_extension+0x457137
000000d3`8e4dfdc0 00007ffd`606e15cd mongod!index_collator_extension+0x4572de
000000d3`8e4dfdf0 00007ffd`62d843d1 KERNEL32!BaseThreadInitThunk+0xd
000000d3`8e4dfe20 00000000`00000000 ntdll!RtlUserThreadStart+0x1d



 Comments   
Comment by Mark Benvenuto [ 20/Jan/15 ]

Here is the actual stack trace. It looks very similar to SERVER-16918.

Child-SP          RetAddr           Call Site
000000d3`8e4deff0 00007ff7`f2234569 mongod!__wt_tree_walk+0x136 [d:\mongo\src\third_party\wiredtiger\src\btree\bt_walk.c @ 116]
000000d3`8e4df070 00007ff7`f225e7db mongod!__wt_btcur_next+0x1c9 [d:\mongo\src\third_party\wiredtiger\src\btree\bt_curnext.c @ 490]
000000d3`8e4df0c0 00007ff7`f1e9e4ba mongod!__curfile_next+0x9b [d:\mongo\src\third_party\wiredtiger\src\cursor\cur_file.c @ 80]
000000d3`8e4df0f0 00007ff7`f1e9fe35 mongod!mongo::WiredTigerRecordStore::cappedDeleteAsNeeded+0x1da [d:\mongo\src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp @ 405]
000000d3`8e4df290 00007ff7`f1b4021b mongod!mongo::WiredTigerRecordStore::insertRecord+0x415 [d:\mongo\src\mongo\db\storage\wiredtiger\wiredtiger_record_store.cpp @ 515]
000000d3`8e4df3e0 00007ff7`f1b40f37 mongod!mongo::Collection::_insertDocument+0x6b [d:\mongo\src\mongo\db\catalog\collection.cpp @ 243]
000000d3`8e4df460 00007ff7`f1db93ba mongod!mongo::Collection::insertDocument+0x1b7 [d:\mongo\src\mongo\db\catalog\collection.cpp @ 202]
000000d3`8e4df560 00007ff7`f1e0384e mongod!mongo::repl::_logOpObjRS+0x29a [d:\mongo\src\mongo\db\repl\oplog.cpp @ 445]
000000d3`8e4df740 00007ff7`f1e04c0a mongod!mongo::repl::SyncTail::applyOpsToOplog+0xae [d:\mongo\src\mongo\db\repl\sync_tail.cpp @ 663]
000000d3`8e4df7e0 00007ff7`f1e05244 mongod!mongo::repl::SyncTail::multiApply+0x22a [d:\mongo\src\mongo\db\repl\sync_tail.cpp @ 376]
000000d3`8e4df980 00007ff7`f1dfed1c mongod!mongo::repl::SyncTail::oplogApplication+0x3d4 [d:\mongo\src\mongo\db\repl\sync_tail.cpp @ 581]
000000d3`8e4dfaf0 00007ff7`f1feba91 mongod!mongo::repl::runSyncThread+0x37c [d:\mongo\src\mongo\db\repl\rs_sync.cpp @ 135]
000000d3`8e4dfd50 00007ff7`f22ef347 mongod!boost::`anonymous namespace'::thread_start_function+0x21 [d:\mongo\src\third_party\boost\libs\thread\src\win32\thread.cpp @ 185]
000000d3`8e4dfd90 00007ff7`f22ef4ee mongod!_callthreadstartex+0x17 [f:\dd\vctools\crt\crtw32\startup\threadex.c @ 376]
000000d3`8e4dfdc0 00007ffd`606e15cd mongod!_threadstartex+0x102 [f:\dd\vctools\crt\crtw32\startup\threadex.c @ 354]
000000d3`8e4dfdf0 00007ffd`62d843d1 kernel32!BaseThreadInitThunk+0xd
000000d3`8e4dfe20 00000000`00000000 ntdll!RtlUserThreadStart+0x1d

Comment by Daniel Pasette (Inactive) [ 18/Jan/15 ]

Can you add some more detail please:

  • Logfile
  • was this the primary or secondary?
  • what were the startup params used?
  • what is the workload?
Generated at Thu Feb 08 03:42:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.