From 2cf3e7006f5273ce7073f81a8f86e96a2c4617b3 Mon Sep 17 00:00:00 2001 From: Matt Bhagat-Conway Date: Thu, 23 Mar 2023 07:32:47 -0400 Subject: [PATCH] suppress leaksanitizer warnings in extract-tests, #6564 When the extractor encounters a lua runtime error, some osmium objects are not freed. In production this doesn't matter because these errors bring down OSRM. In the tests we catch them to ensure they occur, and the leaksanitizer flags them. --- scripts/ci/leaksanitizer.conf | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/scripts/ci/leaksanitizer.conf b/scripts/ci/leaksanitizer.conf index 9f0e08c19..27c16d04a 100644 --- a/scripts/ci/leaksanitizer.conf +++ b/scripts/ci/leaksanitizer.conf @@ -6,3 +6,12 @@ # #1 0x7f7ae595d13e (/usr/lib/x86_64-linux-gnu/libtbb.so.2+0x2213e) leak:libtbb.so + +# The extract-tests leak some memory in the tests to confirm that +# lua errors print tracebacks. +# This appears to be because when these tests throw exceptions, the +# osmium objects being processed are not freed. In production this doesn't +# matter, as the exceptions bring down the entire osrm-extract process. In the +# tests, we catch the error to make sure it occurs, which is why the +# leaksanitizer flags it. +leak:extract-tests \ No newline at end of file