-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Workload Resilience
-
WR Prioritized list
-
None
-
None
-
None
-
None
-
None
-
None
-
None
An update to Linux kernel 6.19 has caused consistent startup issues (crashes) with MongoDB 8.0+. Strong confidence this issue is in the TCMalloc repo, related to TCMalloc violating the upstream rseq ABI. TCMalloc contributors are aware of this issue.
Impact
Any customer downloading MongoDB 8.0+ and using kernel version 6.19 will get crashes upon trying to run MongoDB. This includes installing using package managers or Docker.
- duplicates
-
SERVER-120238 SIGSEGV (Exit Code 139) exactly 30s after start on AMD Zen 5 due to hardware Shadow Stacks (user_shstk) clashing with coroutines
-
- Closed
-
-
SERVER-121377 mongod crashes with SEGV in mongo::admission::ThroughputProbing::_run exactly 60 seconds after startup
-
- Closed
-
-
SERVER-121885 Mongod crashing on Linux Kernel 6.19.8 - even after setting < Environment="GLIBC_TUNABLES=glibc.pthread.rseq=0:glibc.cpu.hwcaps=-SHSTK">
-
- Closed
-
-
SERVER-122741 MongoDB 8.2.5 (tcmalloc-google) SIGSEGV crash loop on Linux kernel 6.19 — stable on 6.18.7
-
- Closed
-
- is duplicated by
-
SERVER-121911 Upgrade tcmalloc
-
- Closed
-
- is related to
-
SERVER-120238 SIGSEGV (Exit Code 139) exactly 30s after start on AMD Zen 5 due to hardware Shadow Stacks (user_shstk) clashing with coroutines
-
- Closed
-
- related to
-
SERVER-122741 MongoDB 8.2.5 (tcmalloc-google) SIGSEGV crash loop on Linux kernel 6.19 — stable on 6.18.7
-
- Closed
-