This is probably not the correct interpretation of this error.
The Win32 error above is more likely to indicate the actual problem.
Flags
Severity
Success
This code indicates success, rather than an error.
This may not be the correct interpretation of this code,
or possibly the program is handling errors incorrectly.
I've got a .NET application that pinvokes several libraries, all 32 bit (the application is 32 bit as well). I recently started getting crash bugs that occurred when the GC started freeing memory, and when I attached I saw that it was an access violation. After some web searches, I [...] read more
I'm trying to test a crash scenario (in an isolated test-app) with normal page heap (not full). I have set up the flags with gflags /p /enable Test.exe and I'm overwriting an integer buffer by one element ... const size_t s = 100; vector<int> v1(s, 0); int* v1_base = &v1[0]; [...] read more
I seem to be experiencing a memory leak in some code that's been in production for a while now (I see the Process\Private Bytes counter rising over time in PerfMon for my process). Note the code works without issue other than the leaking. The code that seems to be responsible [...] read more
I have a strange problem, if I deploy my app through visual studio as debug or release version all is working well. But if I publish it to the store and download it from there the app crashes after Launcher.LaunchFileAsync or FileOpenPicker. When my app launches for example the default [...] read more
I'm a newbie for .Net and trying to use managed threading. I couldn't find any problem in my code, but it triggers an exception when the Thread Ends. Something like: Unhandled exception at 0x5cbf80ea (msvcr90d.dll) 0xC0000005: Access violation reading location 0x000000d7. #include "stdafx.h" using namespace System; using namespace System::Threading; #define [...] read more