LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Can I browse all ActiveX references in memory?

Hi,

Out of curiosity, is there a way to browse all of the ActiveX objects in memory?  Or at least the ones initialized from LV?  If you have a ton of objects floating around out there, it would be handy to have such a function to help you close them when you're done with them.

Thanks,
Nick
"You keep using that word. I do not think it means what you think it means." - Inigo Montoya
0 Kudos
Message 1 of 5
(3,029 Views)
Hi Nick,

That's a valid suggestion for the LabVIEW developers (post it using the "feedback" link on ni.com/contact), but I'm afraid that it would invite customers to mess up things by not keeping references in a short leash and closing in the right order when done.

In case you want the closest to this kind of feature, try the Request Deallocation function and place it inside the VI that holds the references. When that VI finishes and returns to the caller, all unused memory will be deallocated.
- Philip Courtois, Thinkbot Solutions

Thinkbot Solutions
0 Kudos
Message 2 of 5
(3,006 Views)
Hi Nick,

I just just checked with R&D and it turns out that the Request Deallocation DOESN'T release the references but only the actual data. If you don't close the references with the Close Reference function, the ActiveX references are not released until LabVIEW is closed.
- Philip Courtois, Thinkbot Solutions

Thinkbot Solutions
0 Kudos
Message 3 of 5
(2,993 Views)
Quick clarification - the references aren't auto released until the top level VI stops running. You don't need to close LabVIEW, just stop the main VI of your application. Of course, this applies only to the IDE. Once you build the app into a DLL or EXE, then the references aren't auto-released until the app exits.
Message 4 of 5
(2,988 Views)
Thanks for the clarification, Brian!
- Philip Courtois, Thinkbot Solutions

Thinkbot Solutions
0 Kudos
Message 5 of 5
(2,960 Views)