-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: 6.0.15
-
Component/s: None
-
Query Execution
-
ALL
db.coll.explain('executionStats').aggregate(pipeline)
give crash
{"t":{"$date":"2024-06-26T22:14:56.627+00:00"},"s":"F", "c":"CONTROL", "id":6384300, "ctx":"conn1","msg":"Writing fatal message","attr":
{"message":"Invalid access at address: 0\n"}}
{"t":{"$date":"2024-06-26T22:14:56.628+00:00"},"s":"F", "c":"CONTROL", "id":6384300, "ctx":"conn1","msg":"Writing fatal message","attr":
{"message":"Got signal: 11 (Segmentation fault).\n"}}
in server v6.0.15 where 'pipeline' is set to a particular complex aggregation query (not shown here as it is from a customer).
- is caused by
-
-
- Closed
-