Project that won't let go of some LVClass Dependencies

[Jim Kring]

I'm seeing a strange problem with my LabVIEW project. Here's what's going on.

I have several classes that were created with the OpenG Reference Object Template. If I have my project open and I load one of these classes into memory (either by opening the LVClass or opening a VI that calls a class member), the LVClass gets added to the Dependencies>>Items in Memory folder. However, when I close the LVClass (or the VI that calls the class members) it does not get removed from the Dependencies>>Items in Memory folder and I have no way of getting rid of it. Worse, if I save the project, close it, and then reopen it, the LVClass still shows up in the Dependencies>>Items in Memory and gets loaded into memory.

Has anyone seen anything similar?

[Aristos Queue]

No such behavior has been reported to me. Haven't ever seen that.

[Jim Kring]

Here is a test project called "TestProject". Note that it depends on the OpenG Class Templates for LabVIEW Object-Oriented Programming being installed using VIPM (but does not requite the Endevo GDS to be installed).

Download File:post-17-1189555403.zip

Note that it has a Parent class with two child classes Child1 and Child2. If you remove either Parent, Child1, or Child2, they will stay in memory (as seen under the Dependencies>>Items in Memory) until all three classes are removed from the project.

[Jim Kring]

[update: Confirmed by NI R&D, CAR Number 4EPEBUCS]

[PaulL]

I'm glad I found this topic because I just encountered the same thing.

A couple notes: The child classes stayed in memory until I deleted the parent even though I changed their inheritance so they no longer inherited from the parent! Moreover, when I opened the .ctl file for one of the (disinherited) child classes in the Items In Memory folder I was not able to close the .ctl window.

[Tomi Maila]

It seems I've missed this topic. There is a simple workaround. Simply open the .lvclass file with a text editor and remove the lines in the items in memory section within the lvclass XML file. Next time you open the class, everything works smoothly.

Tomi

[Jim Kring]

QUOTE(Tomi Maila @ Dec 12 2007, 11:50 AM)

It seems I've missed this topic. There is a simple workaround. Simply open the .lvclass file with a text editor and remove the lines in the items in memory section within the lvclass XML file. Next time you open the class, everything works smoothly.

Yes, that works for me too. I mentioned that at the bottom of my original post

Cheers,

[Aristos Queue]

QUOTE(Paul_at_Lowell @ Dec 12 2007, 01:42 PM)

A couple notes: The child classes stayed in memory until I deleted the parent even though I changed their inheritance so they no longer inherited from the parent! Moreover, when I opened the .ctl file for one of the (disinherited) child classes in the Items In Memory folder I was not able to close the .ctl window.

A class will stay in memory as long as there are any data instances of the class lingering around on VIs that aren't members of the class. That means hiding in the operate data of controls/indicators (controls of type LabVIEW Object or LVVariant are common hiding places), or even just sitting in terminals.

The inability to close the .ctl window is a new one. I haven't heard of that before. If you can get it reproducible, please post it to ni.com so it gets investigated and CAR'd.

[Dan Bookwalter]

QUOTE(Aristos Queue @ Dec 12 2007, 03:26 PM)

The inability to close the .ctl window is a new one. I haven't heard of that before. If you can get it reproducible, please post it to ni.com so it gets investigated and CAR'd.

I had this same thing happen last week , i will see if i can reproduce it.....

Dan

[gmart]

QUOTE(Aristos Queue @ Dec 12 2007, 02:26 PM)

A class will stay in memory as long as there are any data instances of the class lingering around on VIs that aren't members of the class. That means hiding in the operate data of controls/indicators (controls of type LabVIEW Object or LVVariant are common hiding places), or even just sitting in terminals.

The inability to close the .ctl window is a new one. I haven't heard of that before. If you can get it reproducible, please post it to ni.com so it gets investigated and CAR'd.

Another "hidden" place is the magic clipboard where LabVIEW items go when they are copied. If you copy a class (I think via CTRL+C), the class is copied to the clipboard and will hang around in memory until the app instance is released (I think).

[Aristos Queue]

QUOTE(gmart @ Dec 12 2007, 03:06 PM)

Another "hidden" place is the magic clipboard where LabVIEW items go when they are copied. If you copy a class (I think via CTRL+C), the class is copied to the clipboard and will hang around in memory until the app instance is released (I think).

This is no different than if you copy any subVI -- the clipboard will hold the VI in memory.