My Win8 program crashed due to blue due to its own exception. Then I turned on the mixed (native + managed) debugger mode in VS and noticed the following:
- Before the application crashes, I display the following message in the output window: A critical error was detected c0000374.
- Then I get the Unhandled exception in 0x77DFAA3C (ntdll.dll) in MyApp.exe: 0xC0000374: the heap is corrupted (parameters: 0x77E0FE38).
- When the debugger is interrupted, I get a "source unreachable" message, and the stack trace information is not useful.
This only happens when the storyboard works, but it's just a wild hunch. Any ideas on how to invoke the root cause of the heap corruption?
PS: I’m not sure if this is generally connected, but I also noticed the following messages in the output output window before the heap problem occurred:
- An exception at the first opportunity in 0x75A84B32 (KernelBase.dll) in MyApp.exe: 0x40080201: WinRT initialization error (parameters: 0x80004005, 0x00000026, 0x14E8F4F4).
- The first chance exception in 0x75A84B32 (KernelBase.dll) in MyApp.exe: 0x40080201: WinRT initialization error (parameters: 0x80070490, 0x00000064, 0x05FFED2C). Firstly, the chance of an exception in 0x75A84B32 (KernelBase.dll) in MyApp.exe: 0x40080202: WinRT conversion error (parameters: 0x80070490, 0x00000000, 0x0000001D, 0x05FFED58).
- First-time exception at 0x75A84B32 in MyApp.exe: Microsoft C ++ exception: EEMessageException in memory location 0x05FFD4F4.
Thank!