Teststand user interface memory increases

[Jeroen-Mechatronics]

Hello,

I am using the "Simple Test Executive Operator Interface Example". However, I have noticed a problem.

After executing a test (using Test UUTs button) the memory is increased.

When I do a lot of tests (which I do) eventually it will take up all my system memory, and the PC will crash...

I do not see this phenomenon using the sequence editor.

I am running TestStand 2010 on a Windows 7 x64 computer.

I think the problem is caused because the user interface saves every execution in the Execution drop down menu.

However, I do not know how to disable this.

Thanks in advance,

Jeroen 

Kverneland Group Mechatronics

The Netherlands

[Norbert_B]

Jeroen,

just to verify your suspicion: Please close all execution once finished in your UI. You can press Ctrl+D (close all finished executions) to do so.

If this removes the issue, you are sure that your suspicion is correct.

There is no automatic way implemented in the UI to close executions once finished. But since the sources are supplied as well, you can insert e.g. a button which connects to unload all finished executions.

hope this helps,

Norbert

[Jeroen-Mechatronics]

Norbert,

I have just verified it. Have been running some sequences, got till 500MB memory. Then pressed ctrl+D, and the memory went down to 90MB.

Is there a way to call a function to clear the finished executions? Then I could call that function every time a sequence is finished...

Jeroen

[Norbert_B]

Jeroen,

for this, you have top modify the UI itself. I hope you are accustomed with how to implement features using the Manager Controls.

You would have to implement something like:

- Wait on Execution to finish (UIMessage: EndExecution), Hint: Callback!

- React by calling AppMgr.CloseExecution (on this finished Execution) or AppMgr.CloseAllExecutions (could create "issues" if not accounted for)

This will immediatly shutdown finished execution(s) which will result in:

- The user possibly cannot read the report in the UI (not necessarily though, depending on the source for the report view)

- The user cannot restart the very same execution

hope this helps,

Norbert

[dug9000]

Why do you have new executions constantly created? That is not the normal behavior of a UUT loop. In a normal UUT loop the same execution just loops over and over again for each UUT. If you are creating new executions within your sequences, you should use the "Close Window when Done" setting on the advanced panel of the sequence call steps. Also you might want to use the "Initially Hidden and Disable Tracing" setting as well if you want these sub-executions to be completely invisible to the user and never get added to the list of executions in the first place.

Hope this helps,

-Doug