100% CPU usage and double timeout bug

[Clayton Yocom]

Originally Posted by Greg McKaskle

It isn't clear why this is called the double timeout, or how the deploy is related to the excessive CPU usage.

I agree, that's why I came here to share my lack of knowledge so hopefully we can not have the bug again. It was termed the double timeout bug by one of the NI guys, Kevin something. He said he had seen it before and hated it.

Originally Posted by Greg McKaskle

We're there diagnostic errors due to timing or other issues? That seems like a possible reason for the CPU usage to be high.

It kept giving us errors as if begin was finishing after periodic tasks and such were opened, refnum errors and such that didn't actually cause anything to break once the robot started, but it did put out LOTS of errors. I can post the code later today when I go to the shop if you'd like.