Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Managed Debugging Assistant 'FatalExecutionEngineError'

Tags:

debugging

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.")
like image 554
abdul sammad Avatar asked Jul 16 '15 10:07

abdul sammad


2 Answers

I know this is an older thread but I recently hit this error and spent about 10hrs diagnosing the issue only to find the latest version of Cylance was interferring. 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.

like image 107
TWells68 Avatar answered Sep 18 '22 10:09

TWells68


Changing to use "Managed Compatibility Mode" is what fixed the error for me in Visual Studio 2015:

Tools menu >Options > Debugging > General > "Use Managed Compatibility Mode"

enter image description here

This Microsoft blog describes what this setting does in a bit more detail.

like image 37
JumpingJezza Avatar answered Sep 19 '22 10:09

JumpingJezza