How to overcome StackOverflowException bypassing unhandled exception handling in .NET

by

There are three kind of so-called “asynchronous exceptions”. That are the ThreadAbortException, the OutOfMemoryException and the mentioned StackOverflowException. Those excepions are allowed to occur at any instruction in your code.

And, there’s also a way to overcome them:

The easiest is the ThreadAbortException. When the current code executes in a finally-block. ThreadAbortExceptions are kind of “moved” to the end of the finally-block. So everything in a finally-block can’t be aborted by a ThreadAbortException.

To avoid an OutOfMemoryException, you have only one possibility: Do not allocate anything on the Heap. This means that you’re not allowed to create any new reference-types.

To overcome the StackOverflowException, you need some help from the Framework. This help manifests in Constrained Execution Regions. The required stack is allocated before the actual code is executed and additionally also ensures that the code is already JIT-Compiled and therefor is available for execution.

There are three forms to execute code in Constrained Execution Regions (copied from the BCL Team Blog):

  • ExecuteCodeWithGuaranteedCleanup, a stack-overflow safe form of a try/finally.
  • A try/finally block preceded immediately by a call to RuntimeHelpers.PrepareConstrainedRegions. The try block is not constrained, but all catch, finally, and fault blocks for that try are.
  • As a critical finalizer – any subclass of CriticalFinalizerObject has a finalizer that is eagerly prepared before an instance of the object is allocated.
    • A special case is SafeHandle’s ReleaseHandle method, a virtual method that is eagerly prepared before the subclass is allocated, and called from SafeHandle’s critical finalizer.

You can find more at these blog posts:

Constrained Execution Regions and other errata [Brian Grunkemeyer] at the BCL Team Blog.

Joe Duffy’s Weblog about Atomicity and asynchronous exception failures where he gives a very good overview over asynchronous exceptions and robustness in the .net Framework.

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. How to change stack size for a .NET program?
  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 deserialize a JObject to .NET object
  12. Why doesn’t await on Task.WhenAll throw an AggregateException?
  13. What causing this “Invalid length for a Base-64 char array”
  14. Why does NotImplementedException exist?
  15. Is it possible to catch an access violation exception in .NET?
  16. Are nested Try/Catch blocks a bad idea?
  17. Service has zero application (non-infrastructure) endpoints
  18. Detecting what the target object is when NullReferenceException is thrown
  19. How to read embedded resource text file
  20. Where Is Machine.Config?
  21. Open Source Alternatives to Reflector? [closed]
  22. Any decent text diff/merge engine for .NET? [closed]
  23. Disable SSL fallback and use only TLS for outbound connections in .NET? (Poodle mitigation)
  24. Logging, Aspect Oriented Programming, and Dependency Injection – Trying to make sense of it all
  25. Get Database Table Name from Entity Framework MetaData
  26. Troubleshooting BadImageFormatException
  27. How to get Windows native look for the .NET TreeView?
  28. .NET core 3.0 and MS Office Interop
  29. XmlSerializer startup HUGE performance loss on 64bit systems
  30. Prevent WebBrowser control from stealing focus?

Leave a Comment