Memory Usage by Sub VIs

[ankit]

Hi

I am using a LabVIEW application for controlling a stepper motor and making sound pressure level measurements. I am using 1/3 Octave band filters from Sound and Vibration toolkit and some other Vis from the same toolkit. My problem is that when I run this on my Desktop machine, it starts eating up memory and the RAM usage keeps on going up which eventually leads to an error message of "Not enough memory". However, the same application runs fine on my laptop. Laptop has LabVIEW 7.0 and desktop has LabVIEW 8.0. There are tons of global variables, refernces, local variables and all the other stuff.  I know that there can atleast zillion things why this is happening. But my question is that, is there a way one can find out which SubVI is causing this memory usage or leakage.

If you need some more information before answering this please let me know because I have to fix this somehow.

Thanks

Ankit

[altenbach]

Does it also happen if you run it on the development system or just as a built application?

If you can run it in the development system on the desktop, you can do some profiling.

Is there any significant difference between desktop and laptop (OS, memory, #of CPU cores, etc.)?

[mikeporter]

The profiler function will show you memory consumption and execution time. But in the mean time:

Do the two computers have the same amount of memory?

How fast is the memory accumulating? Are we talking a matter of minutes or more like hours before it errors-out?

Also be looking at arrays that you are building in the application. Be looking for logic that is constantly adding onto the arrays, but not taking things off.

Mike...

[ankit]

Hi

Laptop info

Dell Latitude D820 2 GB RAM, 2.0 GHz processor

Desktop info

Dell Precision PWS670 3 GB RAM, 3.4 GHz processor (" not enough memory" error message seen on desktop)

I think by development system you mean the VI. Yes I am running the VI on both the machines. If I can do some profiling on a VI please let me know how?

Thanks

Ankit

[mikeporter]

I don't have access to a V8 system right at the moment, but in V7 you go to the Tools menu and select Advanced > Profile VIs... Do you have the Pro version? I think the profiler is only availible with the PDS.

Mike...

Message Edited by mikeporter on 07-31-2007 02:46 PM

[Brian_R]

You can also use the Diagram Disable structure to "comment" out code and find out which VIs might be causing this.  You can perform this in a binary search and you can usually narrow it down really quickly.