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
- lengyueCopper ContributorI have the exact same issue. System: macOS Monterey. Chip: Apple M1 Pro. Device: MacBook Pro (16-inch, 2021).
- welsonsunCopper Contributor
Since my previous post, I have switched to a 14 inch M1 Pro MBP, with latest native version Edge, sometimes the problem still occurs. More often after idling for a night than normal usage during daytime.
Anyway, it should help if people can click "..." on the up-right corner -> "Help and Feedback" -> "Send Feeback".
- trootersCopper Contributor
welsonsun Thank you for the reminder. I'll start submitting the feedack when i see this. If others submit as well perhaps it will build up enough feedback/diagnostic data for Microsoft to investigate.
When i submit feedback, it does give me the option to include attachments. I will open Activity Monitor and take a process sample and include that, and submit regularly.
Others, please do the same!
- jkristiaCopper ContributorI have started seeing the same issue.
I have used Edge since it was released, and only recently have I noticed it running at 100%.
I hope it will be fixed soon - quinncom2Copper Contributor
I wrote a script to detect when Microsoft Edge gets stuck at 100% CPU. It displays a notification if Edge is using more than 90% CPU continuously for more than 10 minutes. Details and instructions in the script comments:
https://gist.github.com/quinncomendant/803eeaa291c390202a74d208836e6bb8
CC: welsonsun TheShaunSaw mikedice417 ThomasNgo trooters johnjansen
- quinncom2Copper ContributorUpdate: I have upgraded to a 2021 MacBook Pro 14" running macOS 12.1 and Edge 96.0.1054.62. It is a new computer with a clean-install OS, nothing copied from my old computer. I'm having exactly the same problem as before. Screenshot: https://i.imgur.com/YMs0sFz.png
(I'm the OP, my my username is different because when I signed in this time it asked me to link to the Microsoft Tech Community and choose a username and it said "quinncom" was not available, even though that is the username I use to sign in with Microsoft. Grr.)- trootersCopper ContributorI have 2021 MacBook Pro 14" running 97.0.1072.69 (ARM64 build) and also have this issue. I can close all windows (Edge process still running) and it takes 100% cpu. Force-Quit will fully close app and resolve the issue. Really annoying as it drains battery and reduces overall battery life by 20%. I have to routinely close all my edge windows to make sure i'm not draining things unecessarily.
- ThomasNgoCopper Contributor
I'm also getting the same issue with my 2017 13-inch MacBook Pro, running BigSur 11.4. I also have a 3s sample from Activity Monitor, if anyone from MS is interested.
- mikedice417Copper Contributor
quinncom same here. If someone from the Edge team is interested I used 'sample' in Activity monitor and captured a 3s sample of the process before I killed it. I keep waking up in the morning with fans on high speed. Switching away from Edge Dev to save my microchips :).
- TheShaunSawSilver Contributor
Tagging johnjansen, to please further look into this issue.
- welsonsunCopper ContributorSame here. Actually I have switched back to Chrome for a month now.