Appcrash on windows server 2008 r2

Fault Module Version: 6. Exception Offset: c6cd2. OS Version: 6. Additional Information 2: bcada7f07e8efa. Additional Information 4: bafcae77edfadfc. Read our privacy statement online:. If the online privacy statement is not available, please read our privacy statement offline:. No idea why this error comes for only few binaries. This has been detected by code running within ntdll.

There may be many reasons for heap corruption, although a buffer overflow is the most likely cause. You will have to continue to debug the application in order to find out what is causing the heap corruption. I'm very interested your issue, did you solve your problem? If so please share the solution with us and mark the right answer. I could able to setup a debug machine to detect this issue in debug environement. I could see that I am getting exception while freeing memory allocated by malloc.

Still looking into the issue as not able to figure out the reason for the same. Now we have a debug setup ready on win and after debugging find that the crash happens while freeing the memory allocated using malloc. I have one question, may sound a dumb one, but i thought it would be good to get clarification on the same. Flow is as described below:. My question is, could this be because of the fact that memory was allocated by runtime. Is thr any such limitation that the dll which allocated the memory only shd free it?

So this should not be the reason for issue which we are facing. One thing i wanted to highlight here: Our application is build on win2k3-sp2 64bit and it works perefectly fine on win2k3 64bit. The heap corruption issues are coming only on win2k8 R2 64bit.

I'm still not getting a clue for this one. I tried to simulate the behavior through a simple app, by allocating less memory, copying a large string into it and then trying to free the memory. I got heap corruption error on both the platforms win2k3 and win2k8.

What i'm not able to understand is that if the issue is in the code then why does the app behave in diff way on win2k3 and win2k8. There is no memory allocation API changed. The only problem was the way we were doing memory allocation using malloc. We were allocating less memory and try to access the memory out of range and later were trying to release the same. Actually the code base was same and the same code was working fine on windows2k3 platform. I would strongly recommend that you make sure that memory allocation is correct in your program.

During the migration from 32bit to 64bit, most of the issue were around memory allocation only. Viewed 1k times. Running the command attrib.

Sudheer Muthusamy Sudheer Muthusamy 2 2 silver badges 14 14 bronze badges. Add a comment. Active Oldest Votes. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown.

The text was updated successfully, but these errors were encountered:. Is this being ran on a VM with limited memory?

That exception code is typically due to a memory overrun. It's possible we are using too much memory during processing since we don't do any smart buffering. Sorry, something went wrong. Ok, we will be looking into this. We plan on merging branch v1. If you don't mind attempting to run it again with the newly compiled version to close a couple potential possibilities it would be greatly appreciated. Happy to download an run again.

Have run existing version on virtual server and had a different problem. Will open another issue. The release has been created. You can get some more detail by running with -l debug. Same result. Ran with "-l debug" but nothing created in executable's folder.

Anywhere else to look? Found the WER file, if that helps. This was very helpful. My research all points to needing to run the Windows System File Checker utility to determine if there is an issue with this dll. The actual C code portion of our code is auto generated by Nuitka then compiled with mingw64 gcc, so I will have to troubleshoot what is happening with those. Possible cross compatibility issue? I set up Python 3. I just saw this comment, unsure of why I wasn't notified by email.