This is still failing.

This still fails with, for example, darwin/native-and-mach-o.objtxt.

Thanks for the CC.

I just did 'check-lld' with an asan Debug+Asserts build and I don't get any failures.

Did you do anything here other than set 'LLVM_USE_SANITIZER=Address' in cmake?

Actually, looks like leaks isn't supported on Mac OS :(

I am able to reproduce this on linux with just

CC=clang CXX=clang++ cmake ../llvm -G Ninja -DCMAKE_BUILD_TYPE=Debug -DLLVM_USE_SANITIZER=Address -DLLVM_ENABLE_ASSERTIONS=ON

and running the test with

./bin/llvm-lit -v ~/llvm/lld/test/darwin/native-and-mach-o.objtxt

I will attach the output. I was also able to reproduce the problem with valgrind instead of asan.

I am doing a build on OS X to see if it reproduces there.

asan leaks

valgrind log

Actually, looks like leaks isn't supported on Mac OS :(

:-(

Do you have access to a linux machine (or is valgrind supported on current OS X? It used to work in the past).

Actually, looks like leaks isn't supported on Mac OS :(

:-(

Do you have access to a linux machine (or is valgrind supported on current
OS X? It used to work in the past).
Afraid I don't have access to a Linux machine. But I was able to repro the leaks in Instruments on Mac OS.

Its coming from MappingNormalizationHeap on at least a few of the tests. In the non io.outputting() case we are allocating (typically) atoms, but somehow these are getting dropped.

I'd have expected all atoms to get to the pass pipeline and only be dropped by (for example) dead strip in the resolver, so i'll need to see where we are dropping the parsed atoms.

Fixed some of these in r263676/r263677.

Looking now to see what else is still leaking.

There were a whole bunch more commits over the last few days. The final known ASan leak was fixed in r264097. UBSan is also clean as of r264234.