This is going to be a short one. It turns out Windows has some tricks up its sleeve. When it recognizes that a process has a crash problem it can apply something called Fault Tolerant Heap (FTH) on it in order to try to prevent future crashes. Of course, when you’re debugging something like a heap corruption this might prevent you from reproducing the bug…
Possibly that’s what happened to me yesterday:
As always, you can rely of Raymond Chen to help us disable this kick-ass feature.
I’ve been chasing this bug for two weeks now and each time I asked “an expert” to have a look, it suddenly stopped reproducing. I still haven’t found what causes my heap corruption, but now I hope I can at least stop looking like an idiot in front of anyone trying to help