chevron-thin-right chevron-thin-left brand cancel-circle search youtube-icon google-plus-icon linkedin-icon facebook-icon twitter-icon toolbox download check linkedin phone twitter-old google-plus facebook profile-male chat calendar profile-male
Welcome to Typemock Community! Here you can ask and receive answers from other community members. If you liked or disliked an answer or thread: react with an up- or downvote.
0 votes
I am receiving the error message for only a specific set of tests in the test fixture. If I switch type mock off the tests run perfect.

Details of the message:

"The runtime has encountered a fatal error. The address of the error was at 0x79e7b7b1, on thread 0x8c4. 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."

Thus far I have been able to reproduce this error consistently but am however unable to place any other code here accept this sample for now:

[Test]
public void TestModelSearchPercentageWithValidMax()
{
decimal? factor = ModelSearch.FindPercentageFactor(25M,null);
Assert.AreEqual(2.0M, factor.Value);
}

The error occurs on the "FindPercentageFactor" signature, it is not even possible to debug and step into that method. I am using VS2005 and TypeMock 3.5.1.0. This fixture also does not make use of any mocking but it does have TypeMock referenced because there is another fixture class in the same assembly which uses mocking.

I can send you the .out files I have, please can you let me know if you need them?

Best regards,
JD
asked by JDGarner (600 points)

3 Answers

0 votes
Taken offline for better analysis
answered by scott (32k points)
0 votes
Hi JD,

I've been searching for help on a similar problem!! Everytime myself and 3 other developers in our team run unit tests in vs2005 that reference type mock I get exceptions as well...I couldn't find any help to resolve this error.

The error we get is ".NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error (7A05E2B3) (80131506)"

Everyone on the net says we must uninstall Windows Workflow extensions in vs...the only problem is we don't even have this install?!?!?

I hope Typemock is able to resolve this as it's a bit irritating.

Ciao
Chavez
answered by Chavez (140 points)
0 votes
This has a patch fix, that will be incorporated in our next service release
answered by scott (32k points)
...