Is it possible to catch an access violation exception in .NET?

by

You shouldn’t. An access violation is a serious problem: it is an unexpected attempt to write to (or read from) an invalid memory address. As John already clarified, the unmanaged DLL might already have corrupted the process memory before the access violation has been raised. This can have unpredicted effects on any part of the current process.

The safest thing to do is to possibly inform the user and then immediately exit.

Some more details: An access violation is an OS exception (a so-called SEH or structured exception handling exception). This is a different kind of exception than the managed CLR exceptions from System.Exception. You will rarely see SEH exceptions in purely managed code, but if one occurs, e.g. in unmanaged code, the CLR will deliver it to managed code where you are also able to catch it1.

However, catching SEH exceptions is mostly not a good idea. Further details are explained in the article Handling Corrupted State Exceptions in MSDN magazine where the following text it taken from:

The CLR has always delivered SEH exceptions to managed code using the same mechanisms as exceptions raised by the program itself. This isn’t a problem as long as code doesn’t attempt to handle exceptional conditions that it cannot reasonably handle. Most programs cannot safely continue execution after an access violation. Unfortunately, the CLR’s exception handling model has always encouraged users to catch these serious errors by allowing programs to catch any exception at the top of the System.Exception hierarchy. But this is rarely the right thing to do.

1This was true until .NET 3.5. In .NET 4 the behavior has been changed. If you still want to be able to catch such kind of exceptions you would have to add legacyCorruptedState­­ExceptionsPolicy=true to the app.config. Further details in the articled linked above.

More Related Contents:

  1. Deciphering the .NET clr20r3 exception parameters P1..P10
  2. What is the correct way to make a custom .NET Exception serializable?
  3. What is a “first chance exception”?
  4. Single-threaded apartment – cannot instantiate ActiveX control
  5. ArgumentNullException or NullReferenceException from extension method?
  6. Difference between “managed” and “unmanaged”
  7. Conditions when finally does not execute in a .NET try-finally block
  8. Should I derive custom exceptions from Exception or ApplicationException in .NET?
  9. Why should I always make my Exceptions [serializable]? (.NET)
  10. How to repair COMException error 80040154?
  11. How to overcome StackOverflowException bypassing unhandled exception handling in .NET
  12. How to deserialize a JObject to .NET object
  13. Why doesn’t await on Task.WhenAll throw an AggregateException?
  14. What causing this “Invalid length for a Base-64 char array”
  15. Why does NotImplementedException exist?
  16. How to call managed code from unmanaged code?
  17. Are nested Try/Catch blocks a bad idea?
  18. Service has zero application (non-infrastructure) endpoints
  19. Detecting what the target object is when NullReferenceException is thrown
  20. Using Json.NET converters to deserialize properties
  21. Strange issue with System.Net.Http 4.2.0.0 not found
  22. What is the difference between List (of T) and Collection(of T)?
  23. Why does a bad password cause “Padding is invalid and cannot be removed”?
  24. How to debug a stackoverflowexception in .NET
  25. Asymptotic complexity of .NET collection classes
  26. How can I produce a “print preview” of a FlowDocument in a WPF application?
  27. Maximum Memory a .NET process can allocate
  28. Why Is ToString() Rounding My Double Value?
  29. Dynamically changing Textbox’s AutoComplete List causes AccessViolationException, any advice?
  30. Found conflicts between different versions of the same dependent assembly that could not be resolved

Leave a Comment