Forum Discussion
100% CPU usage since Edge 105 on Mac M1 ?
After browsing for a little while, CPU usage increases to 100%. When I checked in Task Manager, it's not related to any specific tab but the "browser" process. Closed all tabs doesn't solve it.
I temporarily switched to 106 (dev) and the issue is gone for awhile but then resurfaces
35 Replies
- Same here, and has been for a long time.
I also confirmed this occurs on both Intel&M1 Mac.
https://techcommunity.microsoft.com/t5/discussions/high-cpu-usage-on-macos/m-p/3064061/highlight/true#M51674 - I can also confirm that this happens also on Intel based Macs, not just on ARM based Macs. The edge team should really fix this problem.
- I have been experiencing this issue on my M1 Macbook air for about 2 weeks.
So surprised that it's still not fixed today; I've already switched to Vivaldi, a much more customizable browser. Maybe I will come back to Edge a few months later. - I have the same issue, I had to stop using Edge because of this issue, when my mac was running hot I knew I had to restart Edge, this bug will eat you battery very fast.
DONRAMON Yep, I've this too. Mine does that while browsing for long time and doing other stuff in the meantime
But also while suspended (closed lid on my Intel based Macbook Pro) I found that the day after my Mac was very warm and fans spinning with noise, open and logged in then checked Activity Monitor and yup, only Edge consuming all the CPU while suspended
- I've also been experience this problem on a M1 pro Macbook for the past two weeks. Closing and reopening Edge will temporarily resolve the problem for a few hours, but the problem eventually comes back.
- Just cam to add that I have been experiencing this for the last 2-3 weeks. I'll always find out because my laptop is way warmer than it should be. And opening activity monitor reveals the high cpu usage. Force quitting Edge fixes the issue of course but it has been happening so frequent I simply stopped using edge entirely.
- I have the same issue, and concur that closing and re-opening Edge removes the problem for an unknown period of time.
- I have been having this same issue with Edge 105.
