summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorChristian Mollekopf <chrigi_1@fastmail.fm>2017-11-12 21:43:15 +0100
committerChristian Mollekopf <chrigi_1@fastmail.fm>2017-11-12 21:43:15 +0100
commit72ed3b5558c59e22e7c674546e99b78d95e84ee8 (patch)
tree8569fc31274cbaf1a49481112fbd5b10d4023418
parentf493a533befb3f76a03992c1e76c3016da72f135 (diff)
downloadsink-72ed3b5558c59e22e7c674546e99b78d95e84ee8.tar.gz
sink-72ed3b5558c59e22e7c674546e99b78d95e84ee8.zip
lsan leak suppressions
We get a lot of known "leaks" from lmdb. Some are willingly (we never close the environment and dbi's), others are likely because lmdb itself is not instrumented.
-rw-r--r--suppressions.lsan4
1 files changed, 4 insertions, 0 deletions
diff --git a/suppressions.lsan b/suppressions.lsan
new file mode 100644
index 0000000..8000d60
--- /dev/null
+++ b/suppressions.lsan
@@ -0,0 +1,4 @@
1leak:mdb_env_open
2leak:mdb_dbi_open
3#Catch everything from lmdb for now
4leak:liblmdb.so