ActiveX in WebBrowser in WinForms crashing whole app?

Trying to catch and ignore Access Violations is a recipe for introducing memory corruption that can corrupt your application's data or settings. You'd be better off figuring out why the ActiveX control is crashing (e.g. Use WinDBG) and addressing that.

If I could catch the Access Violation, I would happily restart the whole app with Application.Restart(). I would hope that would get me out of further memory corruption in that session; this could lead to perpetual restarts, but that is better than the whole process exiting. (Cheers for the great fiddler2!) – Russell Aug 2 at 10:37 I've provided WinDBG logs to the developers of the ActiveX object, and they're 'looking into it'.

:-) – Russell Aug 18 at 9:49.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.