Comment by kentonv

I patched the free() implementation itself, not the code that calls free().

I did, of course, test it, and anyway we now run into the "freed memory" pattern regularly when debugging (yes including optimized builds), so it's definitely working.