The last supression rule (`leak:libasan*`) would match almost all detected cases, since the first line is almost always something like that: #0 0x7f71040d85bf in __interceptor_malloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:69 Not sure if that was already the case when this suppression rule was added, or if things changed in newer versions of ASAN/LSAN...