Deubg Warnings in TS3.5

[Rafi2003]

Hi,

Is there any explanation to the Debug Warnings received at the end of the test?

Here's for example the beginning of the list I'm receiving:

References to PropertyObjects were not released properly.
    Total number of objects: 10929
    Number of top-level objects: 188

    Note: Some top-level objects may be included if they are referenced by
    an incorrectly released top-level object. For example, an unreleased
    SequenceContext object references a SequenceFile object.

    The following top-level objects were not released:

        Executions [3 object(s) not released]

        Files [1 object(s) not released]
            SequenceFile #1:
                Path: R:\NPI\TESTER\Work\PIZZA\Seq\NTN313AC.seq

        PropertyObjects [174 object(s) not released]
            PropertyObject #1:
                Type: Boolean
                Value:True

            PropertyObject #2:
                Type: Obj

Can I use this info in order to improve my code?

Thanks

Rafi

[~jiggawax~]

Hey Rafi,

It would be helpful to have an overview of your program.  I'm most interested to see if you are using LabVIEW or calling DLLs. 

This error is caused by having a non-empty object reference that is leaking.  Most likely referencing objects correctly will fix the issue.  Let me know what your program is doing and I might be able to give more insight.

Regads,

[Anand_Jain]

Hi

TestStand 3.5 reports any "PropertyObjects" which are not released correctly in debug warnings.

In the above text it looks like you are not releasing 3 executions and may be a sequence file.

I would track down all "Execution" object references that you get in your application and make sure they are released correctly.

Also I would track down the sequence file reference and make sure that it is also released properly.

Thank you

Anand Jain

National Instruments

 The following top-level objects were not released:

        Executions [3 object(s) not released]

        Files [1 object(s) not released]
            SequenceFile #1:
                Path: R:\NPI\TESTER\Work\PIZZA\Seq\NTN313AC.seq

[Rafi2003]

Hi and thanks for your response,

how can a sequence not be released?  I don't have a clue as to what I'm looking for.....

What does it mean that a sequence has not been released?

Thanks

Rafi

[Tyler T.]

Rafi,

Are you programmatically loading a Sequence File?  If you are loading a Sequence File using the Engine.GetSequenceFileEx call, the Sequence File must be released.  Releasing a Sequence File simply means that the Sequence File is unloaded from memory.  If you have called GetSequenceFileEx you must also call Engine.ReleaseSequenceFileEx to ensure that memory for the Sequence File is released.

If you are not programmatically loading a Sequence File, then I'm not exactly sure why you are getting the message.  However, if you give me some detail about what Sequence Files are involved in your application, then I may be able to replicate it and provide you with an explanation of the warning.

Thanks,

Tyler T

[RayFarmer]

Rafi,

You seem to have several Messages on the go, are these related ,

http://forums.ni.com/ni/board/message?board.id=330&message.id=9360#M9360

Maybe if you could post an example which highlights your problem, this would help everyone.

Regards

Ray Farmer

[Rafi2003]

Hi Tyler,

I don't have any such call to this sequence.   This sequence, by the way, is the main sequence of  my test program, so, I assume it is called by the User Interface.  I"m using the NI TestExec.c (full version).    I use the TS3.0 interface because I did some very minor changes to it (resize the different panles and location on the screen...).  I tried it also with the UI provided with TS3.5 and it does the same thing.

Any idea as to how to track down who is calling this sequence.   I already ran multiple file searches and couldn't find it.

Thanks

Rafi

[Rafi2003]

Some more info....

I experimented with my code to see at what stage the error occurs.

The FileLoadUnload Callback does not do it!

It happens in the setup of my mainSequence at the first time a CVI dll is called by TS.

It is my understanding the the Sequential model calles the mainSequence....(which is exactly the sequence file which is not being release) , and I assume it is there were it is supposed to be release.  Is that so?

Any more suggestions how to debug this problem?

Thanks

Rafi

[Tyler T.]

Rafi,

It is difficult to tell why you are getting this message without first seeing your code.  An experiment you should try is to build a sequence that consists of a single call to the CVI DLL that you mentioned.  If you are still getting the message, then it is probably something to do with what that code performs.  If possible, could you then post the CVI code module and sequence.  If I see the same behavior, I may be able to tell you why you are getting the message.

Thanks,

Tyler T