TestStand Not Release Previous Memory When Run New Execution

Updated Feb 1, 2024

Reported In

Software

  • TestStand

Issue Details

I'm facing an issue where the used memory while running the sequence file was not released when it came to running for new execution as shown below:

Task Manager:
1. First Execution: 431.0 MB memory usage
image.png
2. Second Execution: 
image.png


 

Solution

This is expected behavior because in default setting TestStand will kept the code module and in the memory until the sequence file is close.

You can programmatically unload the module to release the memory after each execution.