Wpf application crashes silently. No execption or error message.

Question

0.00/5 (No votes)

See more:

Hi,
My 32bit C# WPF application is crashing when I try to open a large data in my datagrids. There is no exception or error message. App just silently disappears.
How can I find the point (or reason) of crash.

I am using Visual Studio 2010 Pro.

Please help.

Thanks,

What I have tried:

I tried using Module window in debug mode but that too disappears as soon as app crashes.

Posted 18-Aug-16 2:05am

Smartguy3k

Updated 19-Aug-16 0:15am

Add a Solution

Comments

Richard MacCutchan 18-Aug-16 8:42am

The only way to do this is by using the debugger and stepping through the code. You must know round about where the crash happens so you can set a breakpoint around there.

Smartguy3k 19-Aug-16 6:16am

Hi Richard, thanks for helping. I tried to step through the code, line by line. I found sometimes the application is crashing even at the closing curly brackets of a function, just when the control is returning back from a function. I do not have any return statement in this function. I may have to keep trying, if I could find anything.
In case you have any more suggestions, please let me know.
Regards,

Matt T Heffron 18-Aug-16 13:55pm

In addition to Richard's advice, I'd add that you probably should enable the debugger to automatically break on exceptions.
That's on the menu: Debug -> Exceptions...
In that dialog, check the "Thrown" column check box for "Common Language Runtime Exceptions"
This will probably give you some false positives (so maybe wait until you're at the last point in running your app before it crashes).
If this doesn't catch it, then you might need to check all of the check boxes!

Smartguy3k 19-Aug-16 6:24am

Thanks Matt, I had no clue that there is such an option in Visual Studio. It didn't solve my issue, but definitely it will be helpful in future for debugging. I checked all the check boxes but the application disappeared (on crash) leaving no sign of error or exceptions, like I never executed. I would call it ninja crash.
Regards,

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-19T00:15: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[^]

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.