Sheffield LabVIEW User Group

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW Tip: Performance & Memory Profile Tool

Got a VI that runs for a while (say a day) but then eventually crashes? Maybe it shows a message like the below:

LabVIEW Tip: VI Memory Leak

Then its likely that you’re running out of memory (often referred to as a memory leak). Find out for sure by using the Performance and Memory Profile tool.

LabVIEW Tip: Profile Performance & Memory Tool

 

This can be access from the menu of any VI by selecting Tools>Profile>Performance and Memory.

This tool allows the user to see how much memory each VI in the application instance is using and how long it takes to execute each VI. VI’s will automatically be organised largest/longest first. If you see a VI that is using more time or memory than all the others, or the amount of memory is increasing then it’s likely that that VI is causing the problem. It’s probably worth leaving this to run for a little while (say an hour).

Common causes of memory leaks are Arrays that simply get larger and larger, references that aren’t closed (especially on file writes), and Clusters within Arrays within Clusters within Arrays (clustersauruses) so see if this could be the problem. Also note that its good practice to always initialise Arrays with their max size.

Want to receive our LabVIEW Tips via email each month? Subscribe to our newsletter and we’ll add you to our monthly mailing list. We will not pass your details on to any third party organisations.

 

The post LabVIEW Tip: Performance & Memory Profile Tool appeared first on Austin Consultants.

0 Kudos
Message 1 of 1
(4,251 Views)