重新启动调试会话后，出现FatalExecutionEngineError [英] FatalExecutionEngineError after restarting debug session

问题描述

几个星期(几个月?)以来，在Visual Studio 2017/2019 Enterprise中重新启动我的ASP.NET应用程序后，有时会遇到以下异常.仅当IIS Express已经在运行我的应用程序并且需要在重新编译后启动新的调试会话时，这种情况才会发生.

Since a few weeks (months?) I've been sometimes getting the following exception after restarting my ASP.NET application inside Visual Studio 2017 / 2019 Enterprise. It only happens when IIS Express was already running my application and I needed to start a new debug session after recompiling.

无论何时发生这种情况，我都必须杀死IIS Express(taskkill /f /im iisexpress.exe)并在VS中启动新的调试会话.我不知道是什么触发了这个问题.某天它开始在VS 2017 Enterprise上发生.也许是因为我收到了一些Win10更新?升级到VS 2019 Enterprise并不能解决问题.

Whenever this happens, I have to kill IIS Express (taskkill /f /im iisexpress.exe) and start a new debug session in VS. I can't figure out what triggers this issue. It started happening on VS 2017 Enterprise some day. Maybe because I received some Win10 update? Upgrading to VS 2019 Enterprise didn't solve the problem.

托管调试助手'FatalExecutionEngineError'
Message =托管调试助手'FatalExecutionEngineError':'运行时遇到致命错误.错误的地址位于线程0x16b8上的0x45b30496.错误代码为0xc0000005.此错误可能是CLR或用户代码中不安全或不可验证的部分中的错误.该错误的常见来源包括COM-interop或PInvoke的用户封送处理错误，这些错误可能会破坏堆栈.'

Managed Debugging Assistant 'FatalExecutionEngineError'
Message=Managed Debugging Assistant 'FatalExecutionEngineError' : 'The runtime has encountered a fatal error. The address of the error was at 0x45b30496, on thread 0x16b8. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.'

报告了一些类似的问题，但是要么不能解决我的问题，要么不适用:

There are some similar issues reported, but either don't resolve my problem or don't apply:

• 托管的调试助手"FatalExecutionEngineError"
  • 我没有使用使用托管的兼容模式".
  • IISExpress设置为x64，因为该解决方案是针对x64构建的.
  • 解决方案的目标是.Net Framework 4.6.1，而不是.Net core.
  • 我们不使用EntityFramework.

  推荐答案

  我不确定我在哪里读到这篇文章，但是显然.NET Framework 4.7.x中存在一个错误导致了此问题.升级到.NET Framework 4.8解决了此问题. (该项目继续以4.6.2为目标)

  I'm not sure where I read this, but apparently there was a bug in .NET Framework 4.7.x that caused this issue. Upgrading to .NET Framework 4.8 resolved the issue. (The project continues to target 4.6.2)

  这篇关于重新启动调试会话后，出现FatalExecutionEngineError的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！