Depends on the application a lot. There is a large constant overhead component; then there is the quarantine that has the upper per-thread limit, which means long-running processes tend to use more RAM with time, but also saturate at some point. This can be tuned with runtime flags.
We often see somewhere between 2x and 3x memory overhead on large programs. On Thu, May 2, 2019 at 1:01 PM David Lam <dyla...@gmail.com> wrote: > > How much extra memory do ASAN builds use? There's a paper from 2012 saying > that: > > https://www.usenix.org/system/files/conference/atc12/atc12-final39.pdf > > AddressSanitizer finds out-of-bounds accesses (for heap, stack, and global > > objects) and uses of freed heap memory at the relatively low cost of 73% > > slowdown and 3.4x increased memory usage, making it a good choice for > > testing a wide range of C/C++ applications. > > Is this still current? > > Thanks! > > -- > You received this message because you are subscribed to the Google Groups > "address-sanitizer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to address-sanitizer+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "address-sanitizer" group. To unsubscribe from this group and stop receiving emails from it, send an email to address-sanitizer+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
