How do I address this error: vstest.executionengine.x86.exe has stopped working?

Question

After adding a new unit test with multiple VS versions running I get this error:

vstest.executionengine.x86.exe has stopped working

in a popup window.

I just discovered that the partial class's ToString() override had a dependency on another object causing a stack overflow. I replaced the generic PropertiesToString with explicit tostring calls on the properties for the new object. — Matt Linder, Nov 15 '13 at 14:32

score 23 · Accepted Answer · answered Nov 18 '13 at 14:20

23

I had to check for recursive calls to resolve(ToString in foreign key mappings). See comment on question for details.

answered Nov 18 '13 at 14:20

Matt Linder

5

Yep, 90% of the time its a Stackoverflow Exception under the hood – Christian Rodriguez Jan 31 '14 at 10:01

1 Answers1