Details
-
Bug
-
Resolution: Duplicate
-
Major - P3
-
None
-
4.2.1
-
None
-
None
-
Fully Compatible
-
ALL
Description
I get these with regular frequency. Here is an example of a build where 2 out of 3 mongod segfaulted in this manner, causing the run to fail:
What additional information do I need to provide? So far I don't know if there is a pattern to these segfaults.
The crash stack (demangled with MongoWatson) is:
Attachments
Issue Links
- depends on
-
SERVER-43079 failpoint triggered by LogicalSessionCacheRefresh
-
- Closed
-