One of the most common contributors to memory growth in TestStand systems is the result collection and reporting process. If result processing and report settings are not configured to conserve memory, you may see memory growth as test results are collected and retained in memory. In test sequences which execute for a long period of time or generate a large number of results, this can eventually result in an out-of-memory error.
The report and database model plugins that ship with TestStand will process result information either during the test sequence (if On-The-Fly Reporting is enabled) or after a UUT is finished testing (if On-The-Fly Reporting is disabled). For this reason, report generation is unlikely to cause problematic memory growth unless a single UUT test generates a large number of results or executes for a long period of time.
Disabling Result Collection
To eliminate result collection and reporting as potential contributors to memory growth, you should disable result collection for all steps and disable all reporting and database logging model plugins.
Complete the following steps to disable result recording for all steps:
- In the TestStand Sequence Editor, click Configure » Station Options and navigate to the Execution tab.
- Enable the Disable Result Recording for All Sequences checkbox.
Complete the following steps to disable reporting and database logging plugins:
- In the TestStand Sequence Editor, click Configure » Result Processing.
- Uncheck the Enabled checkbox for all Report or Database plugins.
After configuring these settings, you should run your test sequence again to determine whether a memory leak is still present. If you no longer see a memory leak, this indicates that the result recording and report generation settings are not configured to optimize memory usage. You can follow the steps in the Addressing Memory Issues with Report Generation in TestStand whitepaper to configure these settings to minimize memory growth in your test system.