#File Error#(103)
-
I am using Visual C++ .NET, version 7.1.3088. When I exit my application in debug mode, I get thousands of error messages similar to the following: #File Error#(103) : {1153563} normal block at 0x0587EED8, 32 bytes long. Data: < { . ?> 14 00 00 00 00 CD CD CD CD 07 28 BD F1 2E 95 99 3F First-chance exception at 0x7c597db2 in mygui.exe: 0xC00000005: Access violation reading location 0x01f0ae20 The memory location 0x7c597db2 is the same in every one of these messages, but the other numbers (1153563, 0x0587EED8, Data) are different for each error display. When I look at 0x7c597db2 in the memory window, it just shows me a bunch of ?? ?? ?? ?? ?? ?? I also tried running this in Purify to see if that helped, but no luck. It causes errors in Purify that basically amount to "something is wrong, fix it before running purify again". Can anyone help? Thanks. :confused:
-
I am using Visual C++ .NET, version 7.1.3088. When I exit my application in debug mode, I get thousands of error messages similar to the following: #File Error#(103) : {1153563} normal block at 0x0587EED8, 32 bytes long. Data: < { . ?> 14 00 00 00 00 CD CD CD CD 07 28 BD F1 2E 95 99 3F First-chance exception at 0x7c597db2 in mygui.exe: 0xC00000005: Access violation reading location 0x01f0ae20 The memory location 0x7c597db2 is the same in every one of these messages, but the other numbers (1153563, 0x0587EED8, Data) are different for each error display. When I look at 0x7c597db2 in the memory window, it just shows me a bunch of ?? ?? ?? ?? ?? ?? I also tried running this in Purify to see if that helped, but no luck. It causes errors in Purify that basically amount to "something is wrong, fix it before running purify again". Can anyone help? Thanks. :confused:
This could be memory leak issue. Try to free the unused memory before exiting the application. Regards, Paresh.
-
This could be memory leak issue. Try to free the unused memory before exiting the application. Regards, Paresh.
I found a bug at application exit time and fixed it. When I fixed it, the problem noted in this thread went away. Here's what it was: bad:
CArray my_array; CMyClass* ptr = new CMyClass; my_array.SetAt(index, *ptr);...later...delete &(my_array.GetAt(index));good:CArray my_array; CMyClass* ptr = new CMyClass; my_array.SetAt(index, ptr);... later....delete my_array.GetAt(index);