|
|
|
 Different approaches to the same problem. Isn't it better to focus on understanding both than to be dogmatic about it? - Greg McKaskle [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| Different approaches to the same problem. Isn't it better to focus on understanding both than to be dogmatic about it? - Greg McKaskle [more] |
|
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#2
27-04-2012, 18:32
|
|||
|
|||
|
Re: 100% CPU usage and double timeout bug
I'm not sure about the double timeout as a cause, but I've seen the effect you've described this year. After some optimization, our code uses about 50% of available CPU, but we still need to use the No-App switch to deploy new code, or we time out during deploy:
1) Flip switch to No-App 2) Software reboot robot 3) Deploy built LabVIEW project 4) Flip switch away from No-App 5) Software reboot robot I've also seen intermittent instances where for some runs the machine will be pegged to 100% cpu, but the issue will not repro once we reboot the machine. 
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Threaded Mode