-17500 System Our of Memory Exception

[FloresFe]

Hey colin.c,

The article mentioned above contains instructions that are specific for LabWindows™/CVI. In summary, it asks you to either upgrade to CVI 2012 SP1 or install a patched .reg file that updates a CVI Key.

Here are a few questions to better understand the issue on your end:

1. When exactly do you get this error? Right after opening the OI or after a few test Runs? Do you see the memory usage increase over time or do you get a sudden peak of memory allocation and then the error?
2. Do you also experience memory growth or even an OutOfMemory Exception when running from the Sequence Editor? if so, could you provide detail on the steps you take until you see the error?
3. Have you done any customization to the default OI Executable?

Thanks in advance,

[colin.c.]

Thanks Feline, good to know and please see my answers below:

1. Error only occurred after running the same sequence (with iteration) for 3+ consecutive days or more. The sequence continues to read data from EUT and writes into a CSV file. The memory usage of TestStand increases slowly over time, then error occurred when memory grow beyond 2+GB...
2. It's for remote laptop to capture data from EUT, hence I've only ran this sequence on the TestStand Operator UI for consecutive days. The error messages normally occurred at steps "prompt message", "if", "end", "wait", and never at any of the .vi. 
3. No customization that I know of. Where (and how) can I check?

Side Note: I have previously disabled everything under "Result Processing" in case that was the contributor or memory growth, it has only delayed the error (i.e. allowed more iterations before out of memory). 

• 

That means something else is still taking up the memory over time. Is there any way to check (or breakdown further) to find out what exactly is taking up the memory during the iterations?

[FloresFe]

Thanks for the quick reply, colins.c.

Regarding answer #3, I'd expect to see customizations in the OI Source Code. If you are not aware of it, that's probably not the issue. Let's keep that part on hold for now.

So, TestStand divides results handling into 2 parts: results collection and results processing.

On the Results Processing part, I see that you are using on-the-fly reporting, which is a good practice for time extensive tests. Also, you noticed that removing the results processing part will delay the error. However, unchecking all result processing strategies only won't prevent TestStand to collect results.

To start checking the results collection process, could you please try the two strategies I highlight in the article Preventing Memory Issues with TestStand Report Generation?

Let me know how it goes.

Thanks,

[GavinChen]

Hi,

I have same issue, could you tell me how to fix this issue?

[colin.c.]

The decision at the time was to work on higher priority issues first and put it aside. Unfortunately this was never revisited since then, thus couldn't help you mate..