Windows System Handle Count Increases When Executing Sequence Call Steps in New Threads from a Loop
Primary Software: TestStand
Primary Software Version: 2.0
Primary Software Fixed Version: N/A
If you create a loop in your sequence which contains sequence calls that will execute the subsequences in new threads, the system handle count will steadily increase if a specific setting is selected in the sequence call step properties. On Windows NT/2000/XP you can view the system handle count during a sequence execution through Task Manager, under the Performance tab in the Totals section. If enough sequence call steps are launched in new threads with this behavior enabled, the system can potentially lock up and become unresponsive.
To remedy this very specific problem you can disable the TestStand sequence call step setting for "Automatically Wait for the Thread to Complete at the End of the Current Sequence", by doing the following:
* Note: This setting causes the TestStand engine to store a thread handle for each sequence thread generated so that it can check its status at the end of the parent sequence's execution to keep the parent from ending while the child threads are still active. You can store your own reference to the thread and obtain the results, status, and error information from the asynchronous call using the TestStand API. To get information about the executing thread, you need to disable the "Automatically Wait for the Thread to Complete at the End of the Current Sequence" box so that TestStand will return control to the following steps. For more information about this, see the KnowledgeBase linked below.
KnowledgeBase 2Q3HDU6E: How Can I Get the Status of Another Sequence Execution?
Report Date: 02/21/2003
Last Updated: 09/29/2017
Document ID: 2UK7QTEV