It's different. The reason valgrind might be better is that it tests production binaries. Having to recompile everything with ASAN is difficult in traditional

It's different. The reason valgrind might be better is that it tests production binaries. Having to recompile everything with ASAN is difficult in traditional 'make && make check' workflows, or if you want to build and distribute tested binaries (although can work in CI if set up in advance, and we do use it sometimes there). ASAN + fuzzing is a great combination.