1. 17
  1.  

  2. 1

    How does this compare to ASAN? ASAN seems very convenient (I think you just pass an extra compiler flag and env var), but maybe IsoAlloc is simpler, or has less overhead?

    1. 2

      Pretty different, I think. Clang’s Address Sanitizer does everything it can to detect any illegal memory access. It’s not just a different malloc, it works by inserting checks into your code. It causes massive slowdown, memory bloat, and code size bloat, so no one would ever use it in production or for a shipping app.

      This allocator seems to be competitive with a regular malloc, just with some defenses against common memory bugs that are often exploited. (I haven’t actually tried it, just skimmed the docs.)