Comment 6 for bug 1376324

It would depend entirely on how much the code touches the heap. In a reasonably efficient project, the heap (structure not content) doesn't change that much. You always have to assume malloc/free/new/delete are slow and should avoid them. So the offending corruption could have happened some time ago.