05-29-2013 10:29 AM
@soupy wrote:
If ordering them to do it doesn't expedite things, how bout this...I'll hand deliver a dozen (or more) kolaches from West to NI headquarters if this makes it into LabVIEW 2013...now your stomach wants you to fix this bug...
Redirect them here and I promise I'll whip them into shape. Honestly. 😄
05-29-2013 10:34 AM
What are "kolaches"? I've never heard of that before.
05-29-2013 10:54 AM
05-29-2013 11:07 AM - edited 05-29-2013 11:08 AM
05-30-2013 08:27 AM
Unfortunately the stable LV2012 SP1 usually crashes more than once a day for me so I didn't run into this issue.
But the important question for me is: does this also happen with compiled applications (built from LV2012)? If yes that would be a complete showstopper for us (and I think not only for us since many measurement applications might run for more than a day).
Does anybody know?
06-04-2013 08:15 AM
Is it a common issue for those who do an upgrade to LV2012 SP1, crashing more than once a day?
It is not worth upgrading for the moment?
06-04-2013 08:49 AM
It doesn't crash on me during "normal" operation, but sometimes when adding/deleting probes on running VIs or switching execution highlight while running, or when compiling an exe or FPGA code. Sometimes it doesn't crash, but the FPGA module throws errors when working with a FlexRIO CLIP and then the only way to recover is restarting LabVIEW.
06-04-2013 09:24 AM
I've had it throw warnings before about wanting to recompile a LV library when trying to access a node's properties. Something about the library where the property VI is located!
06-12-2013 10:34 AM
Hello everyone,
We are aware of the issue (CAR 387557) as aCe pointed out. I know this thread has gone a bit cold, but I am interested in getting as much information about your systems as possible to help characterize the bug. For those being affected, can you please personal message me so that I can get some more information about your system (specifically I am interested in a Technical Report from the Measurement & Automation Explorer and a copy of your LabVIEW.ini file).
Thanks for your help,
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments
06-12-2013 11:11 AM
Has anyone run into this issue on a system running 2012 SP1?
Thanks,
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments