Source of mystery crashes

[Jeff]

Hi Sub -

You may already know about his, but I just read the following on a blog

The great news about the .NET Framework 2.0 is that unhandled exceptions, no matter where they come from, now cause termination of the app. You also have the chance to debug the unhandled exception if you have a JIT debugger installed. If you haven't installed an AppDomain.UnhandledException delegate and you're using multiple threads in your console or Windows Forms applications, you'll definitely want to add one when you port your code to the .NET Framework 2.0 because you may have been silently losing threads all along.

Maybe this is what has been happening with the errors that people have reported that show up i nthe system event log but not the gbpvr.exe.log file. Do you have a AppDomain.UnhandledException delegate installed to catch errors from background threads? I assume a plugin with background threads (which I for one use) could be the culprit.

Update: I added a AppDomain.UnhandledException handler to the video archive plug-in to see what would happen and I found two unhandled exceptions in the commongbpvrutilities library that I had missed. I have corrected these for the next release of my plug-ins. Perhaps other plug-in writers have exceptions in background threads that were being missing in .net 1.1 as well.


Jeff

[sub]

Yes, I had read that this was the new behavior, but I was aware I could use this AppDomain.UnhandledException handler. I'll add one for the next build. Thanks for pointing it out.

[jksmurf]

The great news about the .NET Framework 2.0 is that unhandled exceptions, no matter where they come from, now cause termination of the app.

I'm not one to pretend I understand this, but is it possible that this has not been implemented yet?

I ask as "maybe" the config locking up I reported in this thread doesn't do this i.e. terminate GBPVRRecordingService.exe??

k.

[sub]

I'm not one to pretend I understand this, but is it possible that this has not been implemented yet?

I ask as "maybe" the config locking up I reported in this thread doesn't do this i.e. terminate GBPVRRecordingService.exe??

k.

I'm not really sure what you mean by 'not implemented yet'. The above is not something that needs to be done - just information. That information being, .NET 2.0 terminates the current process if the unhandled exception is thrown.

I used the info Jeff supplied above to add a handler that logs this type of problem occuring. If it happens, then the last few lines of a GB-PVR log will contain the following type of message:

9/4/2006 3:02:39 PM.625 ERROR [7] FATAL UNHANDLED EXCEPTION:: System.AccessViolationException: Attempted to read or write protected memory.

[sub]

I ask as "maybe" the config locking up I reported in this thread doesn't do this i.e. terminate GBPVRRecordingService.exe??

I've looked into this and commented in the linked thread.