1) The script may be attempting to access array elements that do not exist.
Check your script for statements that use array variables. If your script does access arrays, make sure that
only existing elements are used. If you attempt to access elements that do not exist, WinRunner will create
If your script does not use arrays, check for static variable declarations and try changing them to "auto"
Change static var = "test"; to auto var = "test";
2) Try to run the script in minimized WinRunner.
Choose Run -> Run Minimized -> From Top or From Arrow
3) You could try and read your table data into an array or multi-dimensional array which would speed up your
test. Working with an array is quicker than accessing a data table.
4) Check the location where the test results are stored. The issue could be due to the number of test results
folders WinRunner is generating, especially if they are being saved to the same drive to which your virtual
memory is allocated. If you need these test results, save them to a folder out on your network, this should
free up resources on your machine. Also, if you are still debugging your test, then run in Debug mode. This
will create a Debug folder which gets overwritten each time you run in Debug mode. Once you have debugged your
script, then run in Verify mode, thus saving your test results.