Forum Discussion
josh_bodner
Microsoft
Jun 09, 2021Dev channel update to 93.0.910.5 is live
Hello Insiders! Today we’re releasing build 93.0.910.5 to the Dev channel. As you can see, this is the first 93, so we’re a little lighter this week than last when it comes to changes, but we’ve st...
Eric_Lawrence
Microsoft
Jun 14, 2021Out-of-memory, Status_Breakpoint, RESULT_CODE_HUNG, and Access_Violation are all possibly symptoms of a bug in the accessibility code. If you visit edge://histograms/UIA, do you have anything listed there?
e.g. if you have the Windows 10 "Text Cursor Indicator" feature enabled, this page will show
Histogram: Microsoft.Accessibility.UIAClient recorded 1 samples (flags = 0x41)
612857738 (1 = 100.0%)
See https://www.reddit.com/r/edge/comments/nx1170/edge_crashes_on_multiple_sites_result_code_hung/h1f9jee for some discussion. You can workaround this issue by closing all Edge instances (verify they're gone in Task Manager) and then starting Edge with
msedge.exe --disable-renderer-accessibility
Kent Herring
Jun 18, 2021Brass Contributor
Disabling the Text cursor indicator feature in W10 fixed the various crashing issues with Edge Dev. I've had it enabled a long time but only recently it became an issue. I had the Histogram code for the text cursor indicator feature. It's gone now. Thanks for the idea!