Forum Discussion
Edge Canary issues
Hey folks, couple more questions for you!
Are you seeing a 'Microsoft Edge has stopped working' popup in addition to the RM reports? Only one, or several? Also, can you check if you've got anything at edge://crashes that corresponds to the RM entries?
The team let me know that these are likely renderer crashes/errors, which is why the browser continues to operate as intended even as you see these entries.
If you have entries in edge://crashes, please submit one of them for review (no need to submit all 200+ that some of you are seeing!)
Update, after applying the Canary build 795 update, I see no more crashes in RM. Looks like the issue is fixed. This is after my observation of about 6 hours.
This was fun, with my RM filled with crash reports of Edge (734 to be precise xD):
Crashes on 9th Feb, starting with Edge Installer crashes
Crashes on 10th Feb
Crashes on 11th Feb
No more crashes after applying the update. Yayy!
- CrazyKatsFeb 12, 2021Iron Contributor
Oddly I did show errors last night immediately after getting .795:
But after an overnight shutdown I have none this AM.
- Rohit YadavFeb 12, 2021Bronze Contributor
For me, just after applying the update, RM does not show any crashes, thankfully. Also, my sync is back up now, syncing items between devices quickly. Yayyy!
For others in this thread who reported crashes, make sure you submit Feedback to the team with Diagnostic Data, which will help in faster resolution of the bug.
- cjahn50Feb 12, 2021Iron Contributor
I can confirm that Version 90.0.796.0 did not report any issues in the RM. So far, so good.
- cjahn50Feb 12, 2021Iron Contributor
Version 795 produces the same Stopped Working messages in the RM.
- UserBNFeb 12, 2021Copper Contributor
FWIW, I'm getting similar and consistent issues with Beta Version 89.0.774.23 (Official build) beta (64-bit). Running Windows 10 Home, Ver 20H2, Build 19042.804. Edge Beta will hang and become unresponsive multiple times a day. Critical events in Reliability History labelled as "Stopped responding and was closed." This is a new problem that was introduced in the latest update for me.