Forum Discussion
DONRAMON
Sep 14, 2022Brass Contributor
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
- HenryOnMacCopper ContributorHow nice to work again with a silent 'Macbook Pro 13" 2019' after 2 weeks of constant fan noice and a battery that was draining...
- younggengCopper ContributorSeems that it is fixed in 105.0.1343.53. Now it has been 4 days and I haven't encountered that problem once.
- abitzsongCopper ContributorI also confirm that on M1 MBA, ver 105.0.1343.53, fixed.
However it's still really frustrating facing this kind of OBVIOUS bug presenting in multiple STABLE officially release versions. It's really not acceptable.- Ian_LewisCopper ContributorStill happening in Dev at least. I would have thought it would be fixed there first. Will try Beta.
- ikjadoonBronze ContributorMicrosoft is now claiming it is "fixed". I'll test soon on my M1 MBA; quite ridiculous to see such bugs in the stable build. Shouldn't these have been caught in Canary & Beta first?
https://www.reddit.com/r/MicrosoftEdge/comments/xmunty/comment/iq5h9ur/?utm_source=reddit&utm_medium=web2x&context=3- drung0365Copper ContributorAppears to be fixed with 105.0.1343.53. For me, leaving Edge open while my computer was in sleep mode for extended periods of time (at least a few hours) would cause 100% CPU usage. Quitting Edge and relaunching would clear it for that time. With 105.0.1343.53, it did not immediately fix it even after quitting and relaunching Edge. However, restarting my machine since the update SEEMS to have fixed the issue.
After I restarted, I used Edge for a little bit and then walked away for about 5 hours. Just sat down and Edge is running fine without slamming the CPU. Just my experience of course...
- jinho1311Copper ContributorI'm on Macbook Pro M1, using the 105.0.1343.53 (Official build) (arm64)
And it still heat up crazily. Please fix this Microsoft! - cugwuhCopper ContributorLooks like its been fixed. Version 105.0.1343.53
- JustinP77Copper Contributor
cugwuh It has definitely not been fixed.
I'm on an M1 Max, and the behavior pattern I (and my brother, also on an M1 Max) have noticed is that, after the machine goes to sleep for an extended period of time (overnight), Edge will be pegged at 100% CPU when the machine wakes up. A restart of Edge always fixes it.
I have not tried other scenarios or shorter sleep sessions, but this scenario always produces the behavior. It is entirely possible that it's a coincidence, though, and it's just misbehaving because it's been open for so long.
- eric123321Copper Contributor
Sep 26, not fixed in my macbook m1 pro, edge version 105.0.1343.53
- ackfoo69Copper ContributorNot fixed for me either. I started Edge and within 30 seconds my fan was on max (this is on MacBook Pro 2019 with Intel CPUs). I'm also on 105.0.1343.53.
- ikjadoonBronze ContributorWhere is the Edge team? This bug has been here for over a week.
Does the Edge team only reply after they've shipped the fix? Seems like a waste of a community. This bug is an embarrassment, draining batteries exceptionally quickly. One of the worst software bugs I've ever encountered on macOS.
I'm glad to see many others have an identical experience. I thought my laptop was going bad: nope, just Microsoft's bug here.
I thought we were on the stable build: shouldn't high-impact bugs like these trigger an "undo commit" situation?- JakeXavierCopper ContributorMS Edge team is over the head with the workload, do not expect a reply anytime soon. So many versions, so many platforms, too many features, extreme workloads, and maintenance become a nightmare.
- Christoph HaugBrass ContributorThat's somewhat depressing but assuming that you have knowledge about the situation in the MS Edge team, thanks for sharing that. It's always good to have realistic expectations.
- abitzsongCopper ContributorSame here. M1 macbook air. I have quitted using Edge since this happened. It's not acceptable.
- ackfoo69Copper Contributor
Thanks to the community for confirming this behavior. The funny thing (not really so funny) is that I had started using Edge on my MacBook Pro because it was so much less processor / fan intensive than Chrome (which is a disaster). Maybe these are changes in the underlying Chromium rendering engine?
In any case, the Edge team should really look into this. Edge now makes my mac unusable if it's not plugged in.