Is there a way to identify which references are open in memory after a vi completes is execution?

[ATE_Dude_22]

I have inherited a bunch of ATE programs, many of which seem to have been written by programmer's that appear to have had very limited experience with LabVIEW at the time they were written. I'm constantly running into problems with these ATE's related to inefficiency and coding issues that sometimes are very subtle, and was hoping that there may be a tool available to help identify issues.

[kbbersch]

Look at the Desktop Trace Execution Toolkit.  It may help you out.

[0utlaw]

Hi ATE_Dude,

Kelly's suggestion is spot-on, the Desktop Execution Trace Toolkit is the way to dig into things like reference handling, although it's rather easy to wander off into the weeds with the wrong filters.

This is a good starting point:

Tutorial: Advanced LabVIEW Debugging: Profiling VI Execution With the LabVIEW Desktop Execution Trace Toolkit

http://www.ni.com/white-paper/8083/en

I believe that using the DETT is also covered in the LabVIEW Performance course.

Regards,