Memory Increase & Crash with Basic Example on Repeat

[EricEvola]

I'd like to understand why memory increases until a crash happens when running even basic examples from the TestStand Editor or User Interfaces.

For example, if I modify the PreUUT of the Computer Motherboard Test shipping example to run indefinitely, TestSTand memory will increase until a crash occurs - at around 500 MB.

 
What is causing the memory to increase?

Also shouldn't it take more than 500 MB to make TestStand crash with reasonable PC specs?

C::\Users\Public\Documents\National Instruments\TestStand 2019 (32-bit)\Examples\Demos\Computer Motherboard Test\LabVIEW

TaskManager.vi in this solution allows memory to be cleared up and can prevent the crash:

https://forums.ni.com/t5/Example-Programs/Task-manager-in-Labview/ta-p/3524904

 Other resources:

https://forums.ni.com/t5/NI-TestStand/memory-leak-teststand/td-p/1637816/page/2?profile.language=en

[WireWeaver]

What is causing the memory to increase?

It's usually the result processing - If you disable the report, do you see the same behavior?

Also shouldn't it take more than 500 MB to make TestStand crash with reasonable PC specs?

In a 32 bit app with LAA enabled you should be able to get over 3GB. The only thing that comes to mind is memory fragmentation if something requires a large block of memory and there's no contiguous block available.

There's a good guide on memory issues in TestStand. It's really more of a series with a bunch of relevant guides in it, including how you can optimize reporting for memory.

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA03q000000x3NpCAI&l=en-US

Hope this helps!

Trent