Trace settings memory leak

[pwaszkewitz]

We have noticed something in TestStand 4.1 (yes, I know how old that is; some systems live longer than others ).

We always switch off tracing in the Station options for performance reasons.

In the Run Options of SequenceCall steps is a "Sequence Call Trace Setting" and as far as I  understand the documentation its only purpose is to disable tracing for that particular call if it is generally enabled.

Now we noticed when this is on "Use current trace settings" the sequence calls seem to leak memory. The amount is apparently something like 80 kByte/call, but this is hard to say as it may depend on the complexity of the sequences called. Also, this setting seems to be inherited, i.e., if we set it like this on a high level in our sequence hierarchy, the execution leaks memory rather fast.

Is this a known problem?

Regards, Peter

[PatrikKaranNI]

Hi pwaszkewitz,

I didn't find anything similar in known issues or Corrective Action Requests for TestStand 4.1.

Could you reproduce the same behaviour also in a new sequence file?

Regards,