[PROBLEM] TestStand ActiveX Out of Memory Error.

[ChristopherPovey]

We have TestStand 3.5 sequences which calls LabView components and LabWindows components (as DLLs).  We keep seeing the following popup box:

ActiveX Error:

sCode = 0xffffbd98

Description: Out of memory

Error accessing item ‘ReportOptions(1).’.

Error accessing item ‘ReportOptions(1).’.

Has anyone seen this error before?  What is the likely cause?

Thanks.

[RayFarmer]

Hi,

Does this error appear at the beginning of a test run, or after lengthy test run?

Do you have a rough idea what the test sequence was doing prior to this error?

A JPG/PNG of the error dialog may help.

Regards

Ray Farmer

[ChristopherPovey]

We have a CVI DLL which uses a third party DLL API to perform 1394 calls to three DAP Technology FireSpy cards.  The error occurs during some of these function calls, but not consistently.

I have been through the CVI DLL code and I am confident that all dynamically allocated memory calls in the DLL are being released.  The same CVI code is being used in a full CVI application (but not as a DLL, directly) and no problems are observed.

Two error boxes seen attached.

[ChristopherPovey]

A suspect.  We use CVI calls the last three parameters are:

short *errorOccurred,

long *errorCode,

char *errorMsg

The last one is used in TestStand as a C String (Const).

I am not a TestStand expert.  Is this pointer automatically created in TestStand?  If so what size is it? 

[herosphro]

Hello Christopher,

Thanks for attaching the captures of the errors.  In order to better understand what is causing the error I was hoping you could provide some more information about your sequence.  I think the questions that Ray asked are very pertinent to better understanding the problems related to your program.  It seems that we may have an issue where we are running the test for extended periods of time and may be putting so much information into the results list that memory begins to fill and we get a crash.  If we are running some of the sequence steps multiple times, or creating large sequences we could see such memory issues.  If you could provide some more specific details about the sequence structure and what steps we are executing at the time of failure that would be appreciated.  I see above you mentioned the dll calls, but it would be helpful to know what other operations may be going on and how/if these steps seem to be related to the failure.

I also notice that your last response was a week ago so if anything has changed since then or if you have been able to narrow down the source of the problem, that information would also be appreciated.

Regards,