Intermittent -17000 TS_Err_OutOfMemory

[Captain_Jack]

Howdy,

We have gotten the error: "-17000 Out of Memory. Error in parameter 4 'result'" in a step that previously executed properly before at least 9 times. We're running an ESS test that ran for 10 cycles and we received this error in cycle 10. The report still generated properly and the amount of data that we collected is a small fraction of the data we've collected on other tests that use a similar design concept. I can't find any additional information on this error in the help or the forum. Can anyone shed some light on the psosible cause of this?

TestStand v3.1

Windows 2000 Server

Running from CVI based Test Executive Interface (Modified).

Thanks for any insights you can provide...

-Jack

[RayFarmer]

Hi,

Is it possible to capture a screen shot of when the error occurs, showing the full error text.

regards

Ray Farmer

[Captain_Jack]

Ray,

No unfortunately, it isn't possible to get a screen shot as it is extremely intermittent and the operators would need to detect it immediately. The TPS is designed to automatically go to cleanup on error, as it frequently runs unattendended for long periods of time. even if we could get a screen shot, what is in quotes is the full message - there's nothing else that would get normally get reported that wasn't, as the sequence it occurred in is marked with tracing turned off and all internal steps have reporting disabled. Information generated in the sequence is passed back as a parameter.

-Jack

[Brandon_V]

Capt. Jack,

This error indicates that one of two things has occured: 1) A memory leak in the software, 2) The computer does not have enough RAM to store everything for your sequence. By the fact that this runs the first 9 times correctly and reports this error on the 10th time, I would lean more toward a memory leak. If you run this for more than 10 cycles, does it error out in 10 still? or only in the last cycle? If it is only the last cycle, what have you added to be done after the last cycle completes? If it is always on the 10th cycle, there is most likely a memory leak in the code you've written. Make sure you are releasing all references (in a database, class call, etc). Also, to determine where this memory leak may be occuring, you can look at the Processes tab in the Task Manager in Windows (Ctrl-Alt-Del). Then go through your sequence one step at a time and see where there seems to be a lot of memory being allocated and never deallocated in the steps.

[DirtyD]

Let me add to Brandon's post that it may not be just memory.  This has happened to me but with 2GB, available ram hasn't been the issue.  It seems to be some lock or limit on system resources.  I have always been able to fix this by closing Internet explorer or Borland C++ builder or Visual Studio and restarting TestStand.