Reputation: 191

Managed Debugging Assistant 'FatalExecutionEngineError'

I'm getting below error:

Managed Debugging Assistant 'FatalExecutionEngineError' has detected a problem in 'C:\Users\App\App.exe'. Additional Information: The runtime has encountered a fatal error. The address of the error was at 0xf5b029e1, on thread 0x72bc. 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.

I get the above error when i execute this statement while debugging.

 LoggerHandler.Info("Executed " & iterations.ToString & " iterations on " & max_processors & " cores in " & Format((Now() - time).TotalSeconds, "0.0") & " seconds.")

Upvotes: 16

Answers (5)

Gabriel G

Reputation: 221

It just happened to me, in my case I was using Spreadsheet Light, I updated all my NuGet packages and the error came up, as posted here, the library was compiled against a specific version of OpenXml and the update broke the whole thing, I downgraded OpenXml version and the problem's gone.

If you've got here because of the Exception message, maybe you're not using Spreadsheet Light, but probably is something related to package versions of your project.

Upvotes: 1

zc2

Reputation: 499

I was able to solve this issue by removing the hidden .vs folder in the solution directory.

Upvotes: 3

TWells68

Reputation: 81

I recently hit this error and spent about 10hrs diagnosing the issue only to find the latest version of Cylance was interfering.

Essentially, Cylance memory protection was blocking local debug of web based projects (ASP and WCF were in our scope). Hope this saves someone else some time troubleshooting.

Upvotes: 8