But the if statement should guard for that. No? I'm not even going to bother putting in braces for the "after" call, but I'm not understanding why I seemed to be getting heap corruption (when I had the "before" call) when I'm not even supposed to be calling it due to the guarded if statement. From MSDN Calling HeapFree twice with the same pointer can cause heap corruption if (g_pTrades != NULL){ ::HeapFree(hHeap, 0, g_pTrades); }
Seemingly Similar Threads
- Re: Please die if you wait "too long" RtlpWaitForCriti
- Please die if you wait "too long" RtlpWaitForCriticalSection
- VB6 and wine_get_unix_file_name
- Problem report: SHRINKER.ERR, fix to DEVICE_Open/CreateFileA?
- Re: Please die if you wait "too long" RtlpWaitForCriti