Conditions when finally does not execute in a .net try..finally block(当 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 块中执行时的条件的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:当 finally 不在 .net try..finally 块中执行时的条件
基础教程推荐
- .NET SerialPort DataReceived 事件未触发 2022-01-01
- 当值可以是对象或空数组时反序列化 JSON 2022-01-01
- 如果有人提交恶意软件Nuget包怎么办? 2022-01-01
- C# 从 List<List<int>> 中删除重 2022-01-01
- Azure Functions:CosmosDBTrigger 未在 Visual Studio 中触发 2022-01-01
- WPF 模态进度窗口 2022-01-01
- 我应该在后面的代码中直接使用 Linq To SQL 还是使 2022-01-01
- 禁止输入少量字符,例如'<'、'&a 2022-01-01
- Moq It.Is<>不匹配 2022-01-01
- 如何使用 .Net 检查 Active Directory 服务器是否已启动并正在运行? 2022-01-01
