Rational Robot stops responding at WaitForSingleObject

Resolving The Problem

To prevent this problem, modify the AUT to yield control to other application while waiting for the child process to initialize itself, or use a Module VP. You could also create a List VP against the Task Manager to achieve this.

For example, instead of a WaitForSingleObject with 0 as the timeout, the developer could set a valid timeout and perform this in a loop.

Also allow other applications to process the Windows message pump if this is currently blocked. See the associated URL for further information about the Windows message pump.

Example:
change from
:: WaitForSingleObject(cProcess. INFINITE);
to
:: WaitForSingleObject(cProcess, 10000); //set timeout value of 10 seconds

Another alternative is to use a Module VP instead of the WatiForSingleObject function (comment out the WatiForSingleObject within the AUTprior to this).

However, please note that a Module VP doesn't capture Console applications processes (e.g. cmd.exe). Robot is not optimized for handling CMD.EXE or Console applications.

If this is the case, you can try to create a List Verification Point against the Task Manager, and set wait flags against this Verification Point.