Forum Discussion
MicrosoftDev channel update to 93.0.910.5 is live
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
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-accessibilityThis resolved the issue with Edge DEV hanging on YouTube, Google Calendar etc. for me. Thanks guys. Just have to remember to remove it in the future.
msedge.exe --disable-renderer-accessibilityEric_Lawrence didn't make any difference...and Accessibility was not enabled. I also didn't see anything in the Dev Tools (F12). For now I'm going to use the Non-Dev version of Edge since I've got a big project I'm trying to go-live with.
- Eric_Lawrence
To clarify, I expect a F12 Console message to be shown for cases where the edge://settings pages go blank, unrelated to crashes or hangs.
It occurs to me that I didn't ask if you're using Edge on Windows 10 20H2 (winver.exe), or on some other platform. On another platform, visiting edge://accessibility and seeing if any of the boxes are checked is a better way of seeing if accessibility is enabled.
If you're crashing somewhere other than accessibility, you might try sharing one of the "Uploaded Crash Report IDs" from edge://crashes and we can take a look at what you're hitting. (Of course, if the crash report has been uploaded, we probably know about the issue already and hopefully have fixed it in Canary or will soon).
Eric_Lawrence would've been nice to tag the rest of us with the same issue 😉
Guess who started using the text cursor indicator a few days before this build came out, after updating to 21H1? This guy!
- Histogram: Microsoft.Accessibility.UIAClient recorded 1 samples (flags = 0x41)612857738 -O (1 = 100.0%)I'm going to try disabling it and restarting Edge now. If YouTube still hangs then it's gotta be something else.
EDIT: It's like magic. YouTube works. themoviedb.org no longer causes the same hung process that tries to gobble all of my RAM up.
I hope I got everyone, and that pings after an edit still work. Check your accessibility settings like Eric_Lawrence mentioned. It fixed all the hangs for me, maybe it will for you too.- Unfortunately that won't resolve it for me since I'm using the Dev channel of Edge on my Mac. I'm not using Win 10 21H1.
