You know how nice it would be if you always wrote exactly what version you're talking about. But if the latter should mean Canary version 86.0.593.0, then I have not been able to detect any problem there. Everything works. No crashes, no delays. However, if this should mean the latest stable version, or version 84.0.522.49, then no problem has been found there either. So you should look for problems in your system, they are somewhere there in Your system, most likely it is damaged User Profile. In the future, please write down which version or versions you are talking about and give a detailed description of the problem. I am currently posting this message here using version of Canary version 86.0.593.0. Really, still cannot find absolutely no problems and moreover, there have not been also with previous.
it is canary and there is more than one user complaining of it crashing, edge has been f**ked up for a few builds now. just because your use case doesn't make things crash doesn't mean the build is fine. i know this thread is a microsoft circle jerk but yall parroted the same thing in the beginning when all you said nothing was wrong with video playback and eventually Microsoft figured out how to copy chrome without breaking it. remember this is why they are not relying on you to test this.
On the latest build edge is crashing when I set the default search to google and type literally anything in the address bar. I am checking a few other PCs to see if this seems to be isolated to any specific windows build. EDIT: 3/3 seems to be a real bug.
I'm experiencing crashes as well when typing anything in the address bar. I'm at Canary v86.0.593.0, and the issue has been repeatable on my end. Edit: I can induce the crash if my search engine is on Google. Configuring the default search engine to other providers such as DuckDuckGo and Bing has not caused me crashes so far from my limited testing.
Seems to have been a server side glitch because all 3 PCs where Edge was crashing for searches with google set as the provider are all functioning normally now.
Yes, seems to have been server-side and resolved for me this morning now as well. That was rough considering it affected Stable channel release as well. My Stable channel Edge crashed yesterday something like 30-40 times while trying to diagnose the issue locally. But I could not get any details to diagnose the cause and therefore ending up being a server-side issue makes sense now. I could only type 1 or 2 characters into the address bar and it would crash the entire msedge.exe and all sub-processes. That is not a good look for Stable channel release. Hopefully Microsoft will give some transparency on what caused that because it was quite wide-spread. Well, for anyone that changes their default search engine, I suppose. If anybody spots any details regarding the server-side cause of the entire browser crash, whether it's a blog post or even little posts on Twitter from Edge developers, please share here because that was certainly interesting.
Me neither, was surprised to see it and even confirmed on multiple PCs just to make sure it wasn't a problem with just 1 specific computer. I don't think it was even an hour between the time I confirmed the bug and confirmed that it was fixed.
looks like the crashing was fixed in the latest build, lets hope they don't break it again with the next update like last time, my crash was not the same as the google search crash. I thought we was no longer spamming this thread with posts about every time edge gets an update?