Hi,
I am trying to document some code written by another developer and don't actually have access to execute the program. Basically, I have found that he dynamically launches a VI that contains three frames within a sequence diagram. The first frame takes care of some quick variable initialization. The second frame is more of a "processing" frame and contains an event structure nested inside of a while loop. The final frame requests that the VI memory get deallocated and then terminates the VI by calling a subvi which uses the VI reference to set the FP.Open property to false and then Abort VI.
Typically, I would have expected the developer to wire in a "close" event tied to a bool control that is then signaled to terminate the while loop / event structure in the "processing" frame of the sequence. This would then trigger the final frame that would "kill" the VI. HOWEVER, what actually happens is that it seems this VI is allowed to execute until a separate dynamically launched VI (which actually started the VI with the "processing" frame) shuts down the "processing" VI by calling FP.Close followed by Abort VI on the VI reference.
My question is whether or not the "processing" VI would be allowed to enter the final execution frame and request deallocation? Or, would this result in a memory leak (the VI that is terminated is updated with images so I would think that a memory leak would be easily detectable unless LabVIEW is doing a good job of automatically freeing this memory).
Thanks for any guidance!
Justin
