I give up solving the problem of overheating and the kernel_task process on the Intel-based MacBook Pro
A ridiculous solution to Intel-based MacBook overheating stupid problem

In this story, I will tell you about the overheating problem with my Intel MacBook Pro, the solutions that I tried, and a funny final solution that made me satisfied me to some extent.
∘ Apple announced the M1 CPU ∘ Microsoft Teams wasn’t the culprit ∘ Why is the kernel_task eating my CPU? ∘ What was the root of the problem? ∘ What solutions did I try? · How did I finally solve the problem? · Final Word · Update
Apple announced the M1 CPU
I was unlucky because shortly after I bought my powerful and expensive MacBook Pro (2019) Space Gray Core i9 64GB 1024GB SSD 16"
, Apple introduced the M1 processor, and then Apple decided to migrate to the M series CPU family for all Mac computer product lines.
At the beginning of this migration announcement, My only concern was about the upcoming macOS updates for Intel-based Macbooks because I am sure in the near future, Apple first won’t implement some cool feature in the newer macOS versions for Intel-based MacBooks and then will announce that we will not support the Intel-based MacBook at all! I have a solution for that. I will migrate back to Linux and will keep my powerful laptop.
But after a while, A more critical problem happened to me: Overheating
Microsoft Teams wasn’t the culprit
The first time I encountered this problem was when I was in a meeting using Microsoft Teams and wanted to share my screen, suddenly, My MacBook’s fan started to fly, and the screen got almost frozen. A couple of months later, I had this problem when I was in a similar situation in a meeting with Zoom. After some investigation, I found that Teams or Zoom are not culprits, and the problem is related to a process called kernel_task
.
Why is the kernel_task eating my CPU?
It seems overheating has been a significant problem for MacBooks for years, at least for Intel versions. Apple’s ultimate software solution to this problem is to spawn a hungry process called kernel_task
and make your MacBook frozen and unusable until it cools down. Read Apple’s official support page on kernel_task:
One of the functions of kernel_task is to help manage CPU temperature by making the CPU less available to processes that are using it intensely. In other words, kernel_task responds to conditions that cause your CPU to become too hot, even if your Mac doesn’t feel hot to you. It does not itself cause those conditions. When the CPU temperature decreases, kernel_task automatically reduces its activity.
What was the root of the problem?
To be honest, I still don’t know the root cause of the problem, but I have a few main guesses. The first candidate is to blame the external monitor because I’ve never had the issue of overheating when not connected to the external monitor (always connected to the external monitor for heavy work!). The second culprit can be doing heavy tasks simultaneously, such as video calling, screen sharing, and running Docker and Kubernetes, IDE, and browser simultaneously. But whatever the reason is, for me, they are considered daily use, and I should use the external monitor or run all these software at once while working and developing. This is the reason why I bought a laptop with this high specification.
What solutions did I try?
My main source to try different solutions was this video: