Debugging help - Project with multiple VIs freezes

[WayneS1324]

I have a project with maybe 50 VIs. Every now and again the main app will freeze (meaning that something somewhere has ran away or something).

My question is... How can I find out which VI is sucking up all of the processor? My guess is that there is a for loop free running somewhere but I don't know where.

LabVIEW 2015.

[DuncanW.]

Hi WaneS1324,

I would recommend checking out this tool for evaluating VI performance. With that many subVI's, this problem may be difficult to track down, but the profile performance and memory window is a great place to start. You also may want to use highlight execution to find any loops that are running excessively, although this becomes tedious and time-consuming very quickly as your program grows larger. Let me know if these tools are able to help you diagnose your issue!

Best,

Duncan Waldrop

[billko]

If the main app is a state machine, you can put some simple debugging stuff right before the case structure that logs the states as they occur.  At least you could follow the bread crumbs and figure out which state is hanging.  Maybe have one before that says "Entering xyz state" and one after that says "Exiting xyz state".

This should probably be a regular feature anyway.

[WayneS1324]

Thanks for the replies.

The main app is a state machine. I did what you suggested in a previous project. I don't know why it escaped me this time.

[billko]

If it can knock it down from 50 possibilities to maybe 5-10, I'd say that's a win.  🙂