VI/Application Memory Footprint

[Sam_Sharp]

I have a question about analysing the memory usage/footprint of a LabVIEW application.

I am aware of the DETT and the VI Timing/Memory profiler but they seem to only show the memory used/allocated in the data spaces for the VI - and not the memory usage of VIs loaded into memory themselves (e.g. preallocated clones, shared clones etc.).

I have quite a large application and after loading the top-level VI when I run it the memory usage of LabVIEW.exe increases by about 1GB. This stays in memory until I close the front panel of the top-level VI. This is similar when the application is built into an executable - it uses about 1GB of memory when launched. 

Is there any way/tool to help determine which VIs/clones are taking up the majority of the memory footprint? I know I can disable parts of the application to help narrow things down but I was wondering if there was another method I had missed.

Thanks in advance.

[Bob_Schor]

Does the "Metrics" property help?  You might need to "attach" this within the VIs you want to test and log the values ...

Bob Schor