Sequence File has not been released

[Rafi2003]

Hi,

After the execution is complete, I get (TestStand 3.5) a debug warning stating that a Sequence file has not been released!

The indicated file is my main sequence. 

What does it mean?

Where and how am I suppose to release it?

Any clue as to where to start fixing this problem?

Thanks

Rafi

[RayFarmer]

Hi Rafi,

Is this using your Operator Interface?

Regards

Ray Farmer

[Rafi2003]

Hi,

Yes.

I'm using the CVI based  operator Interface from the TS3.0 package, although I'm using TS3.5.  (reason is because I made some changes to the older version)

Is there any change to the Operator Interface in TS3.5?

Thanks

Rafi

[Patrick_P.]

Hey Rafi,

I was looking at the differences between the TestStand 3.1 interface and the TestStand 3.5 interface, and I did not see any major differences.  Does the 3.5 interface run without this error?  Were you able to run the interface in previous versions of TestStand without this error?

[Rafi2003]

Hi Patrick and thanks...

1) Running the test with TS3.5 UI causes the same warnings.  I began to see the warnings only after upgrading to TS3.5.  The feature of displaying the warnings did not exist before TS3.5. 

2) Please note that the test runs fine. The warnings show up only after I exit the UI. 

3) I noticed that if I only run the FileLoadUnload sequence and then I exit, I don't get the warnings.  However, If I run only one step in the MainSequence, then, I get the warnings.

4) It is possible to set an option in order not to see the warnings, but I prefer to show them in order to catch any bug in my software.

Thanks

Rafi

[Patrick_P.]

Hey Rafi

This error is occurring because somewhere there is a reference to an object that is not being closed.  The first step would be to open just your operator interface(OI) and close it to see if the error occurs.  If it does, then there is an object in your OI that isn't being closed.  The next step would be to open an example sequence file in your OI and see if the error occurs.  If it does, most likely the problem is still within your OI.  If the example sequence file runs fine, then the problem is in your sequence file itself.  Usually this error occurs in code modules that are being called and not in code that is native to the TestStand API.  The native API tries to close everything for you to avoid this problem. 

Thanks,