托管调试助手'FatalExecutionEngineError'0xc0000005 [英] Managed Debugging Assistant 'FatalExecutionEngineError' 0xc0000005

问题描述

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

Managed Debugging Assistant 'FatalExecutionEngineError' : 'The runtime has encountered a fatal error. The address of the error was at 0x641ad419, on thread 0x5d0c. 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.'

这似乎仅在使用Asp.Net Core 1.1和仅适用于.net的实体框架（非EF Core）。它也并非一直都发生，但是它总是在EF调用期间发生。

This only seems to happen using Asp.Net Core 1.1 and only with entity framework for .net (not EF Core). It also does not happen all of the time, but when it does it's always during an EF call.

我已经尝试过启用使用托管的兼容模式，如所述< a href = https://stackoverflow.com/questions/31451431/managed-debugging-assistant-fatalexecutionengineerror>此处，但似乎没有什么不同。

I've tried enabling "Use Managed Compatibility Mode" as described here, but it doesn't seem to make a difference.

推荐答案

我收到了 FatalExecutionEngineError：'运行时遇到了致命错误。错误的地址是线程0x4520上的0x72d41302。错误代码是0xc0000005，而在Visual Studio 2017中运行一个简单的hello world应用程序。

I was getting "FatalExecutionEngineError' : 'The runtime has encountered a fatal error. The address of the error was at 0x72d41302, on thread 0x4520. The error code is 0xc0000005" while running a simple hello world application in Visual Studio 2017.

通过使用x64模式进行调试解决了该问题。

Resolved the issue by using x64 mode for debug.

这篇关于托管调试助手'FatalExecutionEngineError'0xc0000005的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！