LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW 2012 runs processor up

Hey Steve,

 

You initially said that it was both LabVIEW's start screen and even structures causing this CPU usage. Lets isolate these two items as I don't think they're related.

 

As to the former start screen item while I have seen the same thing personally I have not found a way to replicate it. Currently I am merely leaving the start screen running when I am not using it and checking the process for CPU usage. In the past restarting the program was all I had to do to fix it.

 

Event structure CPU usage should be easier to troubleshoot. If possible could you post the code which was doing this?

 

Regards,

Craig H. | CLA CTA CLED | Applications Engineer | NI Employee 2012-2023
0 Kudos
Message 11 of 28
(1,385 Views)

It seems like any code will cause the CPU rise.  I had a LV project open and one VI open (not running) and left it idle for about an hour.  When I come back CPU is up to 25% from LV2012.  It does seem to be focused on CPU 0 and one other wierd thing is that the OS context is VISTA not Win7.  When I start using LV2012 again it sometimes goes back to normal but other times I have to close out and restart LabVIEW.

 

I have attached a screenshot of the resource monitor.

 

LV2012 CPU usage

0 Kudos
Message 12 of 28
(1,367 Views)

Good morning, I have the some problem. My processor runs at 50% with the project stopped. I have to close labview to solve the problem. No solution?

0 Kudos
Message 13 of 28
(1,346 Views)

After the CPU usage goes up does running the VI then stopping it cause the usage to go back down?

Regards,
Isaac S.
Applications Engineer
National Instruments
0 Kudos
Message 14 of 28
(1,320 Views)

This happens when VIs are not running, just a project open.  Sometimes when you close the project the processor will go down but other times I have to completely close LabVIEW.

0 Kudos
Message 15 of 28
(1,318 Views)

To me it is exactly the same

0 Kudos
Message 16 of 28
(1,303 Views)

I wouldn't be surprised if it's something in the project environment, as i've several times have added a testprogram (700 vi) to a project and suddenly got 10 times longer opening, save and editing times. I think it can be related.

 

What happened to me: Moving a global variable in a block diagram for pure look reasons, no change in function shouldn't cause a recompile, but even if it do, it should be very fast and quick. Without project environment i was, when creating a project and adding the main.vi it caused 10 sec recompile ...

 

Could it be related?

 

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 17 of 28
(1,292 Views)

I am having the same problem.  The CPU is at 50% on LabVIEW 2012, if I have a project open.  This is with nothing running, and it is using up 50% (1 entire core of 2 on the CPU) continuously, literally for days solid.

 

I am using 12.0f3 (32 bit), on WinXP Pro version 2002 Service Pack 3, on a Dell Latitude E6400 dual-core CPU (P8700 at 2.53GHz) laptop.

 

This is very frustrating, I can't do any work efficiently on the entire computer if LabVIEW is running.

 

 

0 Kudos
Message 18 of 28
(1,261 Views)

Craig and I are currently working to document this issue as it occurs intermittently depending on the system.  Does restarting LabVIEW take care of it or are you forced to restart your computer?

Regards,
Isaac S.
Applications Engineer
National Instruments
0 Kudos
Message 19 of 28
(1,225 Views)

Restarting LabVIEW corrects it for me.  I have not had to restart my pc yet to get the processor down.  When you say document this, are you able to recreate?  Are there any hints as to what is causing it?

0 Kudos
Message 20 of 28
(1,223 Views)