Hacker News new | past | comments | ask | show | jobs | submit login

Except you have no idea how many people are affected, you only know how many A) noticed, B) traced the culprit back to kernel_task, and C) reported it. That's likely a very small percentage of the afflicted population.

I'm also not sure how you explain a CPU pegged by a kernel process on a machine which should be doing almost nothing as "shear chance". That's a bug.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: