My Oracle Support Banner

Oracle ODBC Driver Memory Corruption On Close MFC Record Set On x64 (Doc ID 1335110.1)

Last updated on FEBRUARY 21, 2019

Applies to:

Oracle ODBC Driver - Version to [Release 11.2]
Information in this document applies to any platform.


When closing a CRecordSet object following an insert or update operation on any underlying table in the database. The database table is updated correctly, but on closing the record set, the heap has been corrupted.

Call Stack :

msvcr90d.dll!_CrtIsValidHeapPointer(const void *pUserData=0x00000000021c0cf0)
 Line 2103    C++
msvcr90d.dll!_free_dbg_nolock(void * pUserData=0x00000000021c0cf0,int
nBlockUse=1)  Line 1317 + 0xa bytes    C++
msvcr90d.dll!_free_dbg(void * pUserData=0x00000000021c0cf0, int nBlockUse=1)  
Line 1258 + 0xe bytes    C++
mfc90ud.dll!ATL::CCRTAllocator::Free(void * p=0x00000000021c0cf0) Line 249    
mfc90ud.dll!operator delete[](void * p=0x00000000021c0cf0)  Line 388    C++
mfc90ud.dll!CRecordset::FreeRowset()  Line 2635    C++
mfc90ud.dll!CRecordset::Close()  Line 1154    C++
Oracle_x64.exe!wmain(int argc=2, wchar_t * *argv=0x00000000002ce1c0, wchar_t
* * envp=0x00000000021c1f10)  Line 95 + 0xd bytes    C++
Oracle_x64.exe!__tmainCRTStartup()  Line 583 + 0x19 bytes    C
Oracle_x64.exe!wmainCRTStartup()  Line 403    C
kernel32.dll!BaseThreadInitThunk()  + 0xd bytes  
ntdll.dll!RtlUserThreadStart()  + 0x21 bytes  




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.