Forum Discussion

josh_bodner's avatar
josh_bodner
Former Employee
Jun 09, 2021

Dev 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...
Ken_LeBlanc's avatar
Ken_LeBlanc
Copper Contributor
Jun 14, 2021

josh_bodner the latest release is causing an "out-of-memory" error when I'm opening Sherlock pages from Epicsystems website. Definitely coincided with the update on the 10th and I've rebooted multiple times with no change.

Eric_Lawrence's avatar
Eric_Lawrence
Icon for Microsoft rankMicrosoft
Jun 14, 2021

Out-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

Resources