LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why is using 100% of a CPU (1 out of 8) when it does nothing

Solved!
Go to solution

@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.  😄

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 11 of 22
(1,405 Views)

What are "kolaches"?  I've never heard of that before.

0 Kudos
Message 12 of 22
(1,402 Views)

Interesting search results.... 😮

 

 

0 Kudos
Message 14 of 22
(1,389 Views)

Unfortunately the stable Smiley Mad 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?

 

 

0 Kudos
Message 15 of 22
(1,355 Views)

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?

0 Kudos
Message 16 of 22
(1,311 Views)

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.

 

0 Kudos
Message 17 of 22
(1,302 Views)

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!

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 18 of 22
(1,291 Views)

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 

 

 

0 Kudos
Message 19 of 22
(1,255 Views)

Has anyone run into this issue on a system running 2012 SP1

 

Thanks,

 

Jeff Peacock 

 

Product Support Engineer | LabVIEW R&D | National Instruments 

0 Kudos
Message 20 of 22
(1,243 Views)