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.[FIXED]Super strange crashing bug
No Longer happening as of Version 79.0.287.0 (Official build) canary (64-bit) Whenever I click in the red area, Edge insider Version 79.0.285.0 (Official build) canary (64-bit), Crashes. by crash I mean it suddenly closes. in this area, the mouse cursor turns from arrow into a hand with pointing finger. by the way the syncs have been in this disabled state for 2 days now!Various Edge Versions On MacOS Big Sur Beta 4 Crashes Very Frequently
Hi guys, I have logged this feedback via the browser (whilst I had the time) but I wanted to see if others are having similar problems. I am confident it is linked to Big Sur as Catalina had no issues at all. The issue: - I run Edge and start using it, sometimes it will last maybe an hour, sometimes only a few minutes and it will terminate. - I do not browse the same combination of sites every time. - I have been forced to use Chrome Canary as an alternative, but this doesn't crash at all. (version 86.0.423.0) - This is a problem with Edge, Edge Beta and Edge Dev too as I have installed all of those and it does the same thing. - Interestingly, just before the last force close, I ran Edge Canary via the Terminal script inside the app icon (show package contents > contents > MacOS) it had shown me this in the Terminal window: [0812/102241.519215:WARNING:process_memory_mac.cc(93)] mach_vm_read(0x7ffee6b73000, 0x2000): (os/kern) invalid address (1) [0812/102242.473112:WARNING:crash_report_exception_handler.cc(258)] UniversalExceptionRaise: (os/kern) failure (5) zsh: segmentation fault My stats: - At the time of writing I was running Edge Canary Version 86.0.605.0 and I am on the Insider Fast ring. - Macbook Air 13 Inch Early 2014 - Big Sur Beta Version 20A5343i (the crashes have happening since Developer Beta 1) I am not looking for an immediate fix, but perhaps some contact with devs and fellow Edge lovers to sort this issue out, I HATE having to use Chrome 😞
MS Edge is crashing with a STATUS_STACK_BUFFER_OVERRUN
Hi, Has someone an idea why Edge (also Goggle Chrome) crashes with a STATUS_STACK_BUFFER_OVERRUN, when we try to start Edge (86.0.622.69, Official build) by an external program (C#, using System.Diagnostics.Process.Start)? As parameter we are giving the Url. It has worked with IE, but now MS Edge is the default browser. Thanks Eric
Reproducible crash adding Edge Apps - happens 100% of the time
OS: Mac OS Mojave 10.14.6 (18G3020) Edge: Version 79.0.309.71 (Official build) (64-bit) Steps to reproduce: 1. Go to any website 2. Click the · · · button > Apps > Install this site as an app What I expect to happen: Edge creates the app and continues functioning. And the new App also functions. What happens: 1. Edge drops the app with its correct icon into my Edge Apps folder and opens it so it appears in my Dock. The new App shows a dot indicating that it's open. 2. Edge goes to permanent beachball until force quit 3. The new App is clickable and can be activated, but has no windows, just a menu bar with all options unselectable other than Quit. The App can be opened and quit but doesn't ever get any windows or do anything (regardless of whether Edge is open, hung, or not running). 4. After Edge is killed I was offered a stacktrace by the OS (attached in case it may be useful) Tried this with the Outlook webapp on my corporate office 365 account and also with a random personal site. Behavior was exactly the same both times.Super High CPU usage on Windows - i9 9900K + Edge insider Canary
Hi, I've been having this problem with Edge insider Canary for almost more than a month, right now it's Version 79.0.305.0 (Official build) canary (64-bit) and the problem still exists. I thought it would fix on its own but no matter how much I waited, it's not getting fixed.. this problem used to happen on my system having Intel i7 7700K and now it's happening on my system running Intel i9 9900K. happens on a variety of Windows 10 insider builds, now it's 18999 1/4 of Intel i9 9900K is used by Edge insider! that's really too much processing power. and it happens very often. most of the time it happens on https://vk.com/feed, YouTube.com and on this forum. I Can't tell what is causing this because: 1. when it happens, the browser hangs and CPU usage and temperature keeps going up until I have to force close Edge from the task manager or keep clicking on the X button on that problematic tab until it comes out of hanging state for at least 1 millisecond and decides to registers my mouse click and closes that tab. 2. when it happens, the browser task manager also hangs so I can't check anything. 3. when it happens, it also prevents me from using feedback smiley button and its problem recording feature. I previously asked developers to Separate that feedback and problem recording functionality from the browser core so that when problems like this happens and the browser itself goes into hanging state and becomes unresponsive, the feedback section would be responsive at all times and record what is wrong with the browser. the problem is not related to any flags or browser settings, not related to smart screen, neither is it related to extensions, I've tested all of that. I hope developers give us some ways to produce a Meaningful and technical feedback for them to find out what's wrong.
