As Kostya said, ASan overhead is not limited to instrumentation of
memory access instructions. One other case that comes to mind: too
many unique malloc/free stack traces can put pressure on StackDepot.
I'd recommend looking at some of the outliers with a CPU profiler.
On Mon, Sep 3, 2018 at 10:5
Hi Guilherme,
Instrumenting all memory accesses is only one cause of slowdown.
Another equally important cause is poisoning the heap memory on malloc/free
and poisoning the stack memory on function entry/exit.
Yet another one, is the growth of total memory usage due to redzones and
quarantine (ext
Hi all,
We are running a few experiments to try to predict the performance slowdown
of Address Sanitizer. Our hypothesis is that an executable with more memory
accesses would take longer than one with fewer. We tried to correlate
the number of loads/stores in the LLVM IR with the slowdown intro
