Forum Discussion
Edge browser 100% CPU, requires Force Quit (macOS Mojave and v91.0.864.48)
I'm reporting a problem I've experienced with Edge since I began using it six months ago. After using Edge for a few hours, it will begin using 100% CPU. According to the Task Manager, it is the "Browser" thread that is using this CPU. If I Quit the application, all the windows close but it doesn't fully quit; I have to do command-option-esc to open the Force Quit window (where it says "Microsoft Edge (not responding)" and then I'm able to Force Quit it. When I relaunch it and re-open the web pages I was using, it works fine (until later that day or the next day, when the process repeats).
Does anyone know how I can troubleshoot this so I can file a useful bug report?
This has happened many times over the past 6 months, over many different Edge versions (I'm always using the latest stable version). I'm not able to reproduce the issue when I want, but it happens regularly every or every-other day.
I'm using macOS Mojave 10.14.6 on a 2015 MacBook Pro.
Edit: It just happened again, so I took some screenshots and attached them below.
34 Replies
I have had the issue again for the past week on my MacBook. It is not consistent, and I only notice it because suddenly the laptop is slightly warm (it is always on power). When I open it, then sure enough Edge is 108% (yes, not just 100%). I kill and restart Edge, and I'm good for some time.
I've been facing this issue for last two days.
Edge Version: 105.0.1343.33
Macbook Pro 16" (Intel) on macOS Version: 12.5.1
Why is it not fixed yet? Edge hogging CPU doesn't really help with my development usage.I'm the original poster of this issue (100% CPU on macOS). I haven't seen this problem occur again since April 2022. I think it has been fixed?
If you have issues on other platforms (Windows, et al), please submit a new issue ticket.UPDATE: soon after posting this, I started having the problem again. It appears the problem was reintroduced with Edge version 105.
- I've had this issue the past month or so, through several versions of the Beta version. I'm on macOS Mojave with a M1 macbook air. I switched to Dev, Version 106.0.1363.0 (Official build) Dev (arm64) and it was fine yesterday but its back since last night. Macbook runs very hot (usually its cool) with Edge and 100% CPU usage.
NashizM
Are you sure you have Mojave running on M1 Air? It says it's impossible to run it on M1. As for the fix of this high CPU usage issue you can try opening Edge through terminal with this command open -a "Microsoft Edge" --args --enable-features=msSmartScreenLegacyDisabled
Seems like it worked for me.
- I'm still seeing this problem with versions 105.0.1343.23 (Beta) and 106.0.1363.0 (Dev). I've tried disabling all extensions but that didn't help. I see there was mention of removing the Collections button as a potential solution, so I'm trying that but did it work in the longer term?
Ian_Lewis I've been continuing to use Edge and the problem has gone away (for the most part). Although, at times by battery plummets and the CPU usage goes up but i haven't been as good at paying attention to the culprit. I will be more attentive to this and if the same issue shows up again, i will post here. What seemed to work for me was disabling the collections button, but YMMV.
- Yeah, many times my laptop goes 100 percent CPU usage. I do not confirm that Microsoft edge is the culprit. it shows many Microsoft edge when I see task manager it performs too many tasks and is at the top of all usages in the task manager app. Dell pc
- Same issue here.
MacBook Pro 14"
MacOS 12.2BrianCHLiu welsonsun quinncom jkristia I updated browser to version 99.0.1150.52 and i also hid my collection button in the toolbar (Appearance settings, Collections Button DISABLE, see screenshot below). That seems to have fixed this issue. I've been running for about 5 days and have not run into the 100% cpu issue again. Battery life has been fantastic.
- Thank you trooters for this recommendation. It has fixed my issues as well. I'm running the latest public build for Edge on MacOS 12.5.1 on a 2019 MBP.
- What I do not understand is why the Edge task manager is not able to identify the specific tab or process responsible for the leak/spike. I will try to get a capture (running safari today), but when I had to kill edge yesterday, the process identified as "browser" was the highest CPU/Memory usage; none of the other tabs, add-ins or internal processes (pre-rendering, network service, storage, etc) even added up to the total indicated in the Edge task manager.
- I've continued to submit feedback reports to Microsoft along with spin dumps and sample dumps. I am narrowing this down... after i close all the browser windows i fire up Browser Task Manager to look at the remaining Edge Tasks running. I have a browser task at 100% CPU, and i start killing off the other tasks until the Browser CPU drops. I'm seeing a pattern where i have multiple "Utility:Collections Entities Service" workers and one of them, after being killed, will allow the Browser Task CPU to drop down to 0. Seems like a bug somewhere in the Collections Entities Service, but of course, i'm not truly debugging this thing just narrowing down the scenarios.
- I can validate this. After killing the "Utility:Collections Entities Service" (I have only one though), the CPU usage dropped to <10
- Usually, I find that closing tabs has no impact right until the last tab. On one occasion about a month back, the CPU decreased gradually with each tab closure, but the Edge task manager still showed only Browser. It's possible driven by some issue affecting the browser code managing tabs, rather than the usage of any individual tab. Most of my open tabs are sleeping anyway as I have quite a few open for convenience.
- Update since my last post:
1. This happens more and more frequently since the latest update. Sometimes after browsing for a while (YouTube, Yahoo), sometimes after one night (closed all tabs previous night), very annoying. Another thing that might help the Edge team is double click the Edge process in activity monitor, and click "sample", save to some file and attach it when reporting.
2. For me, I have switch to ungoogled-chromium. Just "brew install --cask eloston-chromium" will do. - I also have the same issue. In fact it has been going on since I started using Edge, but seems to come and go. I recently moved from Dev to Beta to try to avoid it, but even Beta has the same problem. Indeed, it is happening right now so I will be restarting the browser yet again (3 times this week so far). Previously I was on MacBook Air 2014 with Big Sur, now on 14" M1 MacBook Pro on Monterey. Latest version of Beta is installed (updates automatic).
