Nov 05 2019 09:01 PM
Nov 05 2019 09:01 PM
I am using Edge dev for several months now and this is the first time it happened.
When I started Edge this morning, the windows opens, but after 2 to 5 secondes edge crashes (the edge window closes). I don't have any warning or error message. I also could see that the new update was apply because one of the tab being loaded was the "welcome back" page after an update is done. Also in the lower left coner I can read something like "processing" before the crash.
I download the lastest update with a different browser and apply it but it didn't fix the crash.
I start Edge without extension with msedge.exe --disable-extensions and no more crash.
But this is the weird part: when I restart edge the normal way, it didn't crash anymore even though I had all my extension opened.
I am on windows 10 1903
Edge : Version 80.0.320.3 (Official build) dev (64-bit)
Nov 06 2019 01:55 AM - edited Nov 06 2019 02:02 AM
same here, and then stop working again after a couple of times. must be an extension. Which one I will need to test by deactivating all and activating one by one .
Looks like it is AdBlock.
I was offered to repair it and since then it works. Cross fingers.
Nov 06 2019 05:38 AM
My experience must be different from other people who claim it to be an Adblock issue. I uninstalled Adblock and still had the issue. Turns out, I could open any other page in Edge Dev but I could not have it start up with Google as my startup screen. Doing so causes the crash for me. As soon as I changed it to the new tab option it started working again.
Nov 06 2019 05:56 AM
Nov 06 2019 06:35 PM
Hi Fred & others,
I have tried everything y'all have mentioned that causes crashing & it won't or doesn't crash. Just works like a charm everywhere I go & everything I try. The crashing is not affecting everyone. However, the Team think they know what is causing it (for some Users) and it will likely be rectified, anon.
Nov 06 2019 09:07 PM
Nov 06 2019 10:33 PM
Good, Fred. Anyone with it should report it. Even, knowing others have done so. Either via or via Edge Insider Support. EIS will reply, even converse with a person, regarding the issue submitted. The issue is known. The developers think they know the cause or the origin of it. There is an effort afoot to rectify it asap.
Just a wee thought (of mine) that it may be particularly challenging as it is not impacting all Users. Anyway, just a thought. But, trust, it will be fixed.
Nov 07 2019 12:23 AM
Nov 07 2019 02:03 AM