-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
None
-
Affects Version/s: 3.0.2
-
Component/s: Querying
-
None
-
Environment:Windows 7 64bit, MongoDB 3.0.2/3.0.3
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Steps to reproduce:
- Execute attached project in c# with a document count of 100000 documents
Actual result:
Assertion: 13548:BufBuilder attempted to grow() to 134217728 bytes, past the 64MB limit. mongod.exe ...\src\mongo\util\stacktrace_win.cpp(175) mongo::printStackTrace+0x43 mongod.exe ...\src\mongo\util\log.cpp(135) mongo::logContext+0x97 mongod.exe ...\src\mongo\util\assert_util.cpp(214) mongo::msgasserted+0xd7 mongod.exe ...\src\mongo\bson\util\builder.h(284) mongo::_BufBuilder<mongo::TrivialAllocator>::grow_reallocate+0x145 mongod.exe ...\src\mongo\bson\bsonobjbuilder.h(226) mongo::BSONObjBuilder::append+0x6f mongod.exe ...\src\mongo\db\query\explain.cpp(236) mongo::Explain::statsToBSON+0x372 mongod.exe ...\src\mongo\db\query\explain.cpp(465) mongo::Explain::statsToBSON+0x1d19 mongod.exe ...\src\mongo\db\query\explain.cpp(455) mongo::Explain::statsToBSON+0x1c3d mongod.exe ...\src\mongo\db\query\find.cpp(863) mongo::runQuery+0x1366 mongod.exe ...\src\mongo\db\instance.cpp(218) mongo::receivedQuery+0x36b mongod.exe ...\src\mongo\db\instance.cpp(400) mongo::assembleResponse+0x352 mongod.exe ...\src\mongo\db\db.cpp(207) mongo::MyMessageHandler::process+0xb8 mongod.exe ...\src\mongo\util\net\message_server_port.cpp(231) mongo::PortMessageServer::handleIncomingMsg+0x573 mongod.exe ...\src\third_party\boost\libs\thread\src\win32\thread.cpp(185) boost::`anonymous namespace'::thread_start_function+0x21 MSVCR120.dll beginthreadex+0x107 MSVCR120.dll endthreadex+0x192 KERNEL32.DLL BaseThreadInitThunk+0x22
Expected result:
No exception, atleast none in the server
Background:
I'm currently evaluating MongoDb and testing several optimistic concurrency check schemes.
That's why I'm building a very long query which looks like this
{id=id1, revision=revision1}or ... or
{id=id1000, revision=revision1000}to see if if my current documents are actually still in the collection and are not updated for unknown reasons.
If this is the wrong category for this bug, please move it accordingly, I imagine it might be a bug in the core project, but my reproduction is in C# that's why I created it for the C# driver.