the windows heap manager can be configured to do this on a per-application basis using the 'gflags' utility. it's a useful debugging tool. you're not assured t

the windows heap manager can be configured to do this on a per-application basis using the 'gflags' utility. it's a useful debugging tool. you're not assured that use-after-free is going to be tightly temporally coupled with the free (a lot of the time it is though) and as more time passes after free() the odds increase that the dangling virtual address is re-allocated. it is also the enemy of performance. you should probably not run production things with the heap configured in this way.