Forum Discussion

jelle_schroer's avatar
jelle_schroer
Occasional Contributor
11 years ago

Runtime error occurring since update to test execute version 11

Since we update our test complete and test execute to version 11.   All most all of our test runs are failing (but not all). When it fails, the test run with test execute seems to fail somewhere d...
joseph_michaud's avatar
joseph_michaud
Icon for Staff rankStaff
11 years ago

Various searches indicate that the message comes from abort() though why the app would call abort() is yet unknown.

 

http://stackoverflow.com/questions/8177152/what-is-the-cause-of-this-application-has-requested-the-runtime-to-terminate-it

http://blogs.msdn.com/b/oldnewthing/archive/2011/12/08/10245330.aspx

 

One possible cause is an unhandled exception.  Another link implies that the app ran out of virtual memory on the 32-bit machine and the solution is to set the application virtual address space to 3 GB.

 

You might try making sure your machine is up to date with patches, do 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' to verify system files (See http://www.howtogeek.com/222532/how-to-repair-corrupted-windows-system-files-with-the-sfc-and-dism-commands/).

 

Is this a 32-bit machine?  In the Task Manager, watch the Commit Size to see if TC/TE gets abnormally large.