Crash when starting a performance/memory profile

[MF]

I too have this problem. I have a LabVIEW program that has about 1000 vi's and the largest VI is about 4 MB. I am running LV 8.5 on a Windows XP machine with about 3 GB of memory and a newer processor. I am using the consumer producer architecture, VI server where I need it, and lots of references. Everytime I try to run the Profile software, LabVIEW crashes and goes away. It seems like it is clean code for as much as it is doing but I have had the following problems besides the "Profile" problem:

1) Everytime I open the main VI , labVIEW does some code compilation and therefore queries me to "SAVE" the main VI everytime I close it even if I made no changes.

2) I am using a Ballard 1553 USB driver and that seems to really hurt the coding. Before I knew to only open the handle one time person LV session, I started to corrupt my resources and lose theability to open other programs (word, outlook, etc.). I have actually had sessions where the main was corrupted to the point of being un-usable because of this driver.

3) When I open my program, it shows 290 MB of memory needed. I do not know how to get memory usage because "Profile" doesn't work.

4) The code takes forever to edit because it is using so much memory. To make a simple change (move a control) will sometime cause LabVIEW to lock up for several minutes and sometimes freeze forever requiring a "kill process" from the Task Manager unless I cannot even the "Task Manager" in which case, I have to restart the machine.

If anyone has had any of these problems and found a way to make coding a beautiful thing again, please let me know.

Michael

[Aaron O]

Similar to what was mentioned previously on this forum, it looks like the profile software on pre-2010 with very large projects such as yours can cause crashing.  I would recommend trying to optimize your project to use less memory in order to minimize your memory issues.  Many times, large memory usage like this is unneeded and should be avoided.

[MF]

How can I optimize the program when I do not know where the memory is being eaten up? I thought using the Profile would tell me that. Is there another way to see memory usage?

Michael

[johnsold]

Michael,

First I would profile individual subVIs to see which ones use lots of memory.  If necessary make little test VIs which call only the subVI being profiled.  Try the ones which have large memory footprints with data sets of various sizes to see how the performance varies with the amount of data.

After you find out where the bottlenecks are, you can make smarter choices about improving the whole program.

Lynn