当 finally 不在 .net try..finally 块中执行时的条件

Conditions when finally does not execute in a .net try..finally block(当 finally 不在 .net try..finally 块中执行时的条件)
本文介绍了当 finally 不在 .net try..finally 块中执行时的条件的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

基本上我听说某些条件会导致 .net 吹过 finally 块.有谁知道这些条件是什么?

Basically I've heard that certain conditions will cause .net to blow past the finally block. Does anyone know what those conditions are?

推荐答案

两种可能:

  • StackOverflowException
  • ExecutionEngineException

当存在 StackOverflowException 时,finally 块将不会被执行,因为堆栈上没有空间可以执行更多代码.当存在 ExecutionEngineException 时也不会调用它,这可能是由于调用 Environment.FailFast() 引起的.

The finally block will not be executed when there's a StackOverflowException since there's no room on the stack to even execute any more code. It will also not be called when there's an ExecutionEngineException, which may arise from a call to Environment.FailFast().

这篇关于当 finally 不在 .net try..finally 块中执行时的条件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!

本站部分内容来源互联网,如果有图片或者内容侵犯您的权益请联系我们删除!

相关文档推荐

c# Generic Setlt;Tgt; implementation to access objects by type(按类型访问对象的C#泛型集实现)
InvalidOperationException When using Context Injection in ASP.Net Core(在ASP.NET核心中使用上下文注入时发生InvalidOperationException)
quot;Overflowquot; compiler error with -9223372036854775808L(编译器错误-9223372036854775808L(Q;溢出Q))
Visual Studio 2010 ReportViewer Assembly References(Visual Studio 2010 ReportViewer程序集引用)
Weird behaviour when I open a reportviewer in WPF(在WPF中打开报表查看器时出现奇怪的行为)
how do i pass parameters to aspnet reportviewer(如何将参数传递给aspnet report查看器)