Questions: Are there any tricks to help identify why a given VI is not fully able to leave memory? Is there a way to access the current refcount of a VI, or otherwise identify why a reference is still held open? Is there any way to *force* all references to a given VI to close? Background: We have a built executable that loads and runs *.vi files (that were not built into the exe itself). We are trying to support dynamic reload of the external VIs from disk. We can get *some* cases to work, but there are some situations where the VI never actually leaves memory (we even explicitly call the "All VIs in Memory" application property, and can see that the VI is never leaving memory). Suspect the problem is that somehow the RTE is incrementing the refcount of the VI. The VIs that we are loading at runtime are themselves pretty trivial, but some of the things we are doing *with* them is nontrivial. There are a lot of VI server calls where we are finding controls on the FP and getting/setting properties. We are attempting to limit the number of references opened to the VI itself to be exactly 1, but I suspect there are some VI server calls that we are doing that are implicitly incrementing the refcount. Has anybody else run into this problem and come up with novel solutions? Are there any tools/tricks we can learn from? (Or even anything that *should* be obvious that I'm just overlooking?). Ideally, I'd like to have a way to say "force this VI to completely leave memory, so I can reload it from disk." If only the "Revert VI" method were available in runtime....

LabVIEW

If available use the Desktop execution Trace Toolkit and check for reference leaks.

Message 11 of 11

(221 Views)

What do you need our team of experts to assist you with?

How can we help?

Please enter your information below and we'll be intouch soon.

This field is required

Preferred communication method

Email Phone call

What do you need our team of experts to assist you with?