References won't close in UserMessage Event Callback example.

[Teds]

I download the following example:

http://zone.ni.com/devzone/cda/epd/p/id/2606.

I was going to use some of the features of this example to pass variables from my OI to TestStand.  Well unfortunately, this example with the modified UserMessageCallback locks up everything with an R6025 error.  Well, it actually will also give me the Property Object warning dialog ONLY if I have the Debug Options set within the Station Options->Preferences tab set to report Object Leaks, otherwise I get the R6025 error.  Only solution is to go to Task Manager and close out LabVIEW.

I attached a picture of the callback, I believe I am closing ALL possible references.  I don't understand why TestStand still thinks that the SequenceContext reference is open?   Is there something I have to do special to close the SequenceContext reference because of the Variant to Data function?

I am running TestStand 4.2.1 and LabVIEW 2010.

Thanks,

PH

[Anand_Jain]

Teds,

Please see the following KB  - PropertyObjects Were Not Released Warning When Using LabVIEW, that shows how to resolve the issue reported in your post.

Regards

Anand Jain

National Instruments

[Teds]

No, that still didnt' close it.  Still indicating that the SequenceContext reference is not being closed properly.

Did I put in the VI correctly?

Thanks,

PH

[Hassan_Atassi]

Hello,

I would try moving everything after the Message Event into the case structure and see if that solves the problem, as it looks like you are experiencing a memory leak.

[Teds]

No, that did not solve the problem.  The dialog box when exiting the application still indicates the SequenceContext Object is not being closed.

A bit more information on my end, when I run the same example with TestStand 4.0 and LabVIEW 8.5 I do NOT have any problems.  It would appear in previous versions of TestStand that the references are being closed.

Thanks,

PH

[Hassan_Atassi]

Hello,

Thanks for the information.  I was wondering if you have installed the TestStand Patch for using LabVIEW 2010.

[Teds]

Yes.  Patches are all installed.

Is this issue reproducible on your end?

Thanks,

PH

[Hassan_Atassi]

Hi Teds,

I will try to reproduce the issue on my end.  However, it looks like you modified the original example slightly.  Did the original example work for you or did it display the same issue?

[Teds]

The original example failed, hence it did not work  Again, it did not work with TS 4.2 and LV 2010.

All I was trying to do is use that example, to pass data from my Operator Interface to TestStand using the SequenceContext.  It was mentioned as an example in a previous post here:

http://forums.ni.com/t5/NI-TestStand/Passing-Variable-from-Operator-Interface-to-Process-Model/td-p/...

I attempted to add a fix for the Variant to Data function per reference to the KB, proposed by Anand Jain, in the previous posts!

In the long run, I will have to go with the method proposed by Ray Farmer. 'The simplest way is just store it in the StationGlobals.'   Not exactly the method I prefer to use, but it seems to be working.

Thanks,

PH