02-18-2009 02:50 PM
Hello all,
I have a fairly large LabVIEW (~500 sub VIs). I am trying to carry out a timing analysis of the whole application. I tried this by enabling the "Timing Statistics" and "Timing Details" on the LabVIEW front panel -> Profiles -> Performance & Memory. When I press on Start, the entire LabVIEW application crashes. I haven't noticed a spike on CPU usage. I repeated the same method on one of the smaller sub VIs and it seems to work fine. Unfortunately, due to IP issues, I can't share it here. Has someone run into similar issues or have potential workarounds?
Thanks,
-Ram.
02-18-2009 08:25 PM
500 VIs really isn't that large, can you perhaps break it into pieces and test them separately?
Mike...
02-19-2009 06:02 AM
Which version of LV?
THere was a bug that would crash LV when using the profiling tool on apps with .... ? The DB Toolkit ? .....I think.
Ben
02-19-2009 08:01 AM
Adding to my previous...
and the
have an umber of listing for crashes when using the profile tool.
Ben
02-20-2009 11:13 AM
Thanks for the suggestions to dig deeper in my application and to refer to http://digital.ni.com/public.nsf/allkb/CAB9E23506CA6A18862572B8001066C6. I found that the VI causing the problem was writing a LabVIEW measurement file. Removing it fixed the problem. This is not entirely captured by the following fix. I have attached the VI incase someone is interested.
| 45MB5LFN | Fixed an issue where LabVIEW hangs when you close the configuration dialog box of the Get Properties Express VI, the Set Properties Express VI, or the Write To Measurement File Express VI. |
Thanks,
-Ram.