Managed Debugging Assistant 'FatalExecutionEngineError'

Question

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.")

When you use a StringBuilder in DllImport https://stackoverflow.com/a/6070008/4841381 — General Failure, Apr 09 '21 at 10:05

score 11 · Answer 1 · answered Jan 18 '17 at 08:40

11

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"

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

answered Jan 18 '17 at 08:40

JumpingJezza

5,498
11
67
106

2

i'm seeing similar errors, and this option not work, can you help take a look here:https://stackoverflow.com/questions/44213605/managed-debugging-assistant-fatalexecutionengineerror-occurred – dingx May 27 '17 at 06:17
2

I have same errors, when I enable "Use Managed Compatibility Mode" it shows me below error when I run the program again: "The runtime has encountered a fatal error. The address of the error was at 0x722f5a90, on thread 0xeb8. 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." NOTE: I'm using [DllImport("swedll32.dll", EntryPoint = "_swe_julday@24")]. Not sure but swedll32.dll is unmanaged c/c++ dll. – Nimesh Vaghasiya Sep 07 '17 at 17:43
nowadays, with VS 2019, this error occurs when the condition on `catch(ex) when (condition)` evaluates to a `NullReferenceException`. When this happens, your app crashes; visual studio throws fatal execution engine error – JobaDiniz May 19 '20 at 12:00

score 8 · Answer 2 · edited Sep 08 '22 at 14:45

8

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.

edited Sep 08 '22 at 14:45

StayOnTarget

11,743
10
52
81

answered Oct 15 '21 at 16:38

TWells68

81
1
1

score 1 · Answer 3 · answered Feb 10 '23 at 23:40

1

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

answered Feb 10 '23 at 23:40

zc2

478
3
7

This solution saved me several hours. – xll Jun 13 '23 at 14:13

score 0 · Answer 4 · edited Aug 28 '18 at 13:47

0

This resolved my issue:

Tools -> options -> IntelliTrace -> General

and check "Events Only" option

edited Aug 28 '18 at 13:47

AymDev

6,626
4
29
52

answered Aug 28 '18 at 12:07

sunm

1
2

3

where this option is coming in vs2017? – karan Jan 23 '19 at 16:40

Managed Debugging Assistant 'FatalExecutionEngineError'

4 Answers4

Linked