-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Minor - P4
-
None
-
Affects Version/s: 3.0.2
-
Component/s: None
-
None
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Looks like this has been happening very consistently for a while.
=================================================================
==21115==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 8 byte(s) in 1 object(s) allocated from:
#0 0x9353e9 in operator new(unsigned long) (/data/mci/shell/src/mongod+0x9353e9)
#1 0x94d2fb in mongo::_initAndListen(int) /data/mci/shell/src/src/mongo/db/db.cpp:456
#2 0x94b04b in mongo::initAndListen(int) /data/mci/shell/src/src/mongo/db/db.cpp:649
#3 0x961f9c in mongoDbMain(int, char**, char**) /data/mci/shell/src/src/mongo/db/db.cpp:895
#4 0x961f9c in main /data/mci/shell/src/src/mongo/db/db.cpp:698
#5 0x7fa3f38cdec4 (/lib/x86_64-linux-gnu/libc.so.6+0x21ec4)
-----------------------------------------------------
Suppressions used:
count bytes template
28 34816 mongo::Client::Client
-----------------------------------------------------
SUMMARY: AddressSanitizer: 8 byte(s) leaked in 1 allocation(s).
It looks like this has something to do with the init of the http interface.
Various suites appear to be effected. jsCore_wt and jsCore_wt_compatibility have some suspiciously short logs prior to failing. I suspect it's the same issue.
- duplicates
-
-
- Closed
-