> I will check if there was any process heap corruption which lead to this issue. The thing is that heap corruption can lead to just about *anything*, and it is often not consistently reproducible, especially across environments. FWIW, i second Lee's suspicion that your problem is heap corruption via a double-free, memory over/under-run, use-after-free, or a similar misuse.