3 ms·
A loop not handling all the cases that can occur in system call (errors or other situations), resulting in infinite execution at 100% CPU, isn't weird at all. I
by kazinator 5y ago
A loop not handling all the cases that can occur in system call (errors or other situations), resulting in infinite execution at 100% CPU, isn't weird at all. It's almost an everyday problem.
Almost every "thread using 100% CPU" bug I've ever debugged was due to blowing through some function that was expected to return the happy case, possibly after blocking for a while, but was instead failing.