-
Type:
Bug
-
Resolution: Community Answered
-
Priority:
Major - P3
-
None
-
Affects Version/s: 5.0.6, 4.4.11
-
Component/s: None
-
None
-
ALL
-
1) Insert a document into a collection ('test' in my code). Fields are irrelevant.
2) From the shell, run below code on the collection.
var my_arr = []
for (var i = 0; i <= 150000; i++) my_arr.push
db.test.aggregate([
{ "this_name_does_not_matter_TWO": "$$value" }
{$project: {
"random_field_name": {
$reduce: {
"input": my_arr,
"initialValue": "this_value_does_not_matter",
"in":}
}
}
}
])1) Insert a document into a collection ('test' in my code). Fields are irrelevant. 2) From the shell, run below code on the collection. var my_arr = [] for (var i = 0; i <= 150000; i++) my_arr.push db.test.aggregate([ {$project: { "random_field_name": { $reduce: { "input": my_arr, "initialValue": "this_value_does_not_matter", "in": { "this_name_does_not_matter_TWO": "$$value" } } } } } ])
A Segmentation Fault occurs when nested documents get to a certain level. On my machine it was ~13000. This isn't terribly important to me (I found it because of a bug in my own code) but I don't think a Segmentation Fault is ever supposed to happen. Also it is fairly simple to reproduce. This crashed both a simple 3 server replica set (will crash secondaries if 'prefer_secondary' is enabled) as well as a single server. The Segmentation Fault seems much more pronounced on the replica set (I am probably just a noob at reading MongoDB status though).
I am running Ubuntu 20.04.3 LTS and I tried this on MongoDB releases 5.0.6 and 4.4.11.