This is a bug to track the progress of enabling malloc/delete/new/free mismatch
checks on Windows.
They were probably disabled because these mismatches are usually safe on
Windows, so there should be quite a few places in e.g. Chromium where these
checks fire.
I think we currently don't have any way to control these checks on per-function
basis, it's either completely off or on.
Original issue reported on code.google.com by timurrrr@google.com on 12 May 2014 at 2:01
Original issue reported on code.google.com by
timurrrr@google.com
on 12 May 2014 at 2:01