.net windows app crash unexpectedly

Question

1.00/5 (2 votes)

See more:

, +

I am getting .net app crash unexpectedly.
My code and everything looks fine.

I am really struggling to figure this out

I got the below information from dump file(.dmp).

he

C#

PID__4120__Date__08_29_2016_Time_11_13_58AM__139__Second_Chance_Exception_C0000005.dmp the assembly instruction at ntdll!RtlpLowFragHeapFree+c5 in C:\Windows\System32\ntdll.dll from Microsoft Corporation has caused an access violation exception (0xC0000005) when trying to write to memory location 0x00000000 on thread 0

What I have tried:

Please help me solve this issue...

This is driving me crazy..

Thanks.

Posted 30-Aug-16 9:51am

Member 12478311

Updated 30-Aug-16 12:23pm

Add a Solution

Comments

ZurdoDev 30-Aug-16 16:21pm

How can we help with such little information?

PureNsanity 30-Aug-16 17:36pm

That error is likely going to be deep in the call stack. When debugging make sure to have the exception settings set to throw all exceptions so hopefully while debugging you can see where this is originating from.

Dave Kreskowiak 30-Aug-16 17:38pm

Well, it looks like your code tried to free a block of memory that was already freed up or it tried to free a block of memory that it didn't own.

Other that, it's impossible to tell you anything useful. We have no idea what your code looks like and no information on what line of code is throwing the exception.

Philippe Mori 30-Aug-16 18:27pm

Is it reproductible? If so, look at available information when the error occurs using a debugger.

Foothill 31-Aug-16 17:40pm

Well, for starters, 0x00000000 is a reserved address in Windows, as it is the NULL address. Most C programmers initialize pointers to the NULL address so programs die in this way so it's clear they forgot to assign something important a value. Since you are getting this particular error, I would start by looking for any points that the code jumps from .Net Managed to Win32 native, like System.IO, and make sure that all the parameters to the call are correct.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Patrice T · Answer 1 · 2016-08-30T12:23:00

You should learn to use the debugger as soon as possible. Rather than guessing what your code is doing, It is time to see your code executing and ensuring that it does what you expect.

The debugger allow you to follow the execution line by line, inspect variables and you will see that there is a point where it stop doing what you expect.
Debugger - Wikipedia, the free encyclopedia[^]
Mastering Debugging in Visual Studio 2010 - A Beginner's Guide[^]
http://docs.oracle.com/javase/7/docs/technotes/tools/windows/jdb.html[^]
https://www.jetbrains.com/idea/help/debugging-your-first-java-application.html[^]

The debugger is here to show you what your code is doing and your task is to compare with what it should do.
When the code don't do what is expected, you are close to a bug.

You need to locate where the exception occurs on your code.
Since the debugger allow to run your program step by step, it should not be too complicated.