http://blogs.msdn.com/kristoffer/archive/tags/Interesting/default.aspxTags: Interestingen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/kristoffer/archive/2009/02/25/outofmemoryexception-is-special.aspxWed, 25 Feb 2009 20:25:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:9444365Kristoffer0http://blogs.msdn.com/kristoffer/comments/9444365.aspxhttp://blogs.msdn.com/kristoffer/commentrss.aspx?PostID=9444365<p>Consider the humble OutOfMemoryException and its most common usage. If it is thrown when the system is well and truly out of memory then how would the system allocate enough memory to create a new instance of OutOfMemoryException? Luckily this problem has a simple solution: OutOfMemoryException is allocated up front so it's available when it needs to be thrown.</p><p>The .NET runtime does first try to create a new OutOfMemoryException instance but if it fails it will fall back to the preallocated instance so there is always an exception available to be thrown. </p><p>Some other exceptions are preallocated: StackOverflowException, ExecutionEngineException, and ThreadAbortException.<br></p><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9444365" width="1" height="1">Interesting.NET