-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Server Security
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Summary
The mongo shell (8.0.35) crashed with SIGSEGV while running jstests/core/queryable_encryption/basic_crud.js. No stack trace file was produced, so the crash is unsymbolized.
Found in MongoDB CI for the mongosync (Cluster-to-Cluster Sync) project. The test runs against a replica set; replication and the cluster itself were healthy at the time.
Log
{"t":{"$date":"2026-11-10T18:33:28.491Z"},"s":"F","c":"CONTROL","id":6384300,"ctx":"js",
"msg":"Writing fatal message","attr":{"message":"Invalid access at address: 0x1aaaa7572d7c0\n"}}
{"t":{"$date":"2026-11-10T18:33:28.491Z"},"s":"F","c":"CONTROL","id":6384300,"ctx":"js",
"msg":"Writing fatal message","attr":{"message":"Dumping siginfo (si_code=1): 0b 00 00 00 ..."}}
{"t":{"$date":"2026-11-10T18:33:28.491Z"},"s":"F","c":"CONTROL","id":6384300,"ctx":"js",
"msg":"Writing fatal message","attr":{"message":"Got signal: 11 (Segmentation fault).\n"}}
resmoke recorded the test as exiting -11 (SIGSEGV). Stack trace acquisition found nothing:
Looking for stacktrace files in './data/db/job0' Found stacktrace files: [] No failure logs/stacktrace files found during unsymbolized stack trace acquisition
What this is not
The crash is in the shell process (log context "ctx":"js"), not in a server node. The four mongod Got signal: 6 (Aborted) entries in the same job log occur 2-3 seconds later (18:33:30.9 - 18:33:31.3) across all nodes of both clusters, which is the test fixture aborting after the test failure, not a server crash. There are no invariant failures anywhere in the job log.
Environment
- mongo shell and mongod 8.0.35-patch-6ae473efe28fa0000784db56, Amazon Linux 2023 arm64
- Replica-set topology; test run under a mongosync 8.0 -> 9.0 migration passthrough suite
- Crash occurred 1.5s into the test, immediately after the shell connected
Caveat
This has been seen once and no stack was captured, so there is not much to go on beyond the faulting address and the test name. Filing so the occurrence is recorded; if it does not recur it may be reasonable to close as cannot-reproduce.
Artifacts
Tracked on the mongosync side as REP-8229.