Unexpected Error

[Data Danger]

:( Could somebody tell me why I might be getting the following error.

 

Tester.exe has had a problem and must close down.

 

In my event viewer the following is shown

 

Faulting application tester.exe, version 5.0.0.0, faulting module unknown, version 0.0.0.0, fault address 0x4de7640a.

 

I have exception handlers in all my coded areas and also a global handler but it does not catch this one.

 

Thanks for your time.

[mskeel]

It's a little hard to say with out seeing any code...

 

Try debugging a little more and see if you can lower it down to a specific area. You could put break point in suspect areas and see if you can get the error to occur between breakpoints.

[Data Danger]

The error only occurrs in the release exe. The error does not happen when you are working on the program. I have left the program running for 5 minutes (just displaying on the screen) and then the error appears. I try to re-trace my steps and nothing happens. It's a pain.

[Data Danger]

:eek: I broke into debugger and the top line of the call stack was

 

System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods+IMsoComponentManager.FPushMessageLoop

 

Any ideas

[mskeel]

Sounds like you've got a whopper on your hands. Are you using any third party controls or anything? What language are you using and do you use unsafe code?

[Tygur]

I can't tell you what you're doing wrong without knowing what you're doing.

 

When you break into the debugger and see the call stack, do any of those lines refer to code you wrote? If so, what does that code look like? Are you doing anything unusual in your app at all?

[Data Danger]

Thanks for replying its good to now that there is help out there.

 

mskeel

Sounds like you've got a whopper on your hands. Are you using any third party controls or anything? What language are you using and do you use unsafe code?

 

I'm using VB .Net and I do have third party controls. About the unsafe code not knowingly.

 

Tygur

I can't tell you what you're doing wrong without knowing what you're doing.

 

When you break into the debugger and see the call stack, do any of those lines refer to code you wrote? If so, what does that code look like? Are you doing anything unusual in your app at all?

 

No none of the line are my code. It does break within the sub main section.

 

-------------------------

 

I'm not sure but think I have addressed the problem. I was using a thread within the program to run a long process and needed to allow the user to click on a cancel button to stop the process if required. The thread was updating a progress bar on my UI. After alot of searching on the web this was the only that I could relate to within my program. I removed the thread and will continue to test without it.

 

It is strange to me why I was able to update and run the program without any immediate error. The program would terminate 5 - 10 minutes after had run the thread and it had finished what it was doing, I could even run the thread serveral times with no problem.

 

Fingers crossed I hope the thread was the problem. I will be doing more testing today and will post my findings here to maybe help others who come across the same problem.

 

Kind Regards