Forum Discussion
Canary and now Dev are unusable
As of Mondays update for Canary and today's update for Canary it is no longer usable as it keeps crashing to desktop and now after todays update for Dev it is doing the same. I am writing this from ...
- Oh, also passing on a workaround that may help in the interim! You may have Accessibility Features enabled unexpectedly; turning off the Windows 10 "Text cursor indicator" might get you back up and running as expected, for example. Eric Lawrence (a Principal on the Edge team who wrote this blog) suggested it might help short term if you'd like to take a look and try the workarounds. https://textslashplain.com/2021/10/12/accessibility-uia-troubleshooting/
Alexandra-R
Microsoft
MicrosoftThank you for submitting (again)! I've grabbed them and linked them to this thread ahead of raising this and a handful of other reports to the team for a closer look. Is there anything in particular that's triggering the crashes -- signing in to something, translating something, anything like that? If it's random, or after a certain amount of time, that's totally fine. Just if a specific feature is triggering it I want to make sure to get that team involved as well.
Anything you do in Canary crashes it, even with todays update, Version 97.0.1072.0 (Official build) canary (64-bit). Clicking the link in the email notice I received about your reply to this thread crashed it. Also, Canary and Dev are not loading the startup pages assigned to them when you start them. They both load the the new tab page.
If you do nothing and just start the browser it stays up. but as soon as you do anything, ie, reply to any threads, click a link, switch tabs.. all crash the browser. I am using beta edge right now as it is not crashing. Also just sent in another feedback for the email link crash....
Dennis5mile
- Alexandra-RThank you! I've gotten this in front of the team and they confirmed this is a known Chromium bug relating to accessibility features. The fix is set to go out tomorrow with Canary 1073, so if you could let me know if you're still hitting this tomorrow after you get the update (and drop a new crash report if you do still encounter it) I'll follow up with the team!
- Will do and thanks for the prompt attention and looking forward to the fix.
Dennis5mile- Alexandra-ROh, also passing on a workaround that may help in the interim! You may have Accessibility Features enabled unexpectedly; turning off the Windows 10 "Text cursor indicator" might get you back up and running as expected, for example. Eric Lawrence (a Principal on the Edge team who wrote this blog) suggested it might help short term if you'd like to take a look and try the workarounds. https://textslashplain.com/2021/10/12/accessibility-uia-troubleshooting/
