How to free up memory while running?

[OnlyOne]

Hello,

i´m using a custom OPUI written in LV.

In there i start TestStand 3.5.

The model of Teststand then starts two parallel-sequences (as "New Execution" that are loaded in Sequence-File-Load and looping all the time.

One parallel-sequence checks the buttons of the OPUI and the other parallel-sequence is controling a climatic chamber. When a special temperature is reched then it executes "Test UUT" of the model-sequence (also as "New Execution").

Everything works fine but someone is eating memory. Everytime when a Test UUT is done the memory goes up. And after it is finished the memory is not released.

So my question is: How can i free up unused memory (like garbage collector) in teststand, or in LV if there is a special action needed.

Or perhaps the teststep-results are not removed? So that i create 100s of new executions and they all keep the results?

I already clicked on "Disable result recording for all steps" in the two parallel-sequences and in all steps in the model. So that i think that only the Mainsequence Callback is creating results.

Has someone any ideas what i can do?

Thanks for everything

[RayFarmer]

Hi,

I would image that the memory increase is probably due to the result collection of the Test UUTs execution.

Do you release the Test UUT's Execution when its done?

Do you use On the Fly result collection?

[OnlyOne]

Currently i think i dont release it.

How do i do this?

I only have a sequence-call to TestUUts in "New execution" (see attachment).

Thanks

[dug9000]

If you have result collection disabled for all of your steps then the memory leak is likely due to something else. You might not be closing a reference that you should be. Try to narrow down which part(s) of your sequence are leaking the memory by either stepping through things one step at a time and looking at memory usage or perhaps by cutting out parts of your sequence until the problem goes away. Also, if it's not your sequence then it might be your custom UI that is leaking the memory, to determine this, try running your sequence in the sequence editor and/or one of the UIs that ship with TestStand and see if the problem goes away.

Hope this helps,

-Doug

[dug9000]

---

@OnlyOne wrote:

Currently i think i dont release it.

How do i do this?

I only have a sequence-call to TestUUts in "New execution" (see attachment).

Thanks

---

If you are running a sequence call to a new execution in a loop, you should make sure that you don't have it set to wait at the end of the sequence (unless you want that behavior) as the sequence will have to hold onto a reference to the execution in order to wait for it.

-Doug

[Sergey_Kolbunov]

This may help