Forum Discussion
Dev channel update to 93.0.916.1 is live
Kent Herring Woody Woodman (WOODY)
Check that discussion from Eric_Lawrence out. Appears to be the same bug, but what do I know?
It should already be fixed in the latest Canary build.
abdelfattah
So, I have one error:
- Histogram: Microsoft.Accessibility.UIAClient recorded 1 samples (flags = 0x41)
612857738 -O (1 = 100.0%)
BUT the recorded number doesn't increase with further invocation of that YouTube example (https://www.youtube.com/watch?v=0mGhhdPgXG8)
Once that Youtube tab has hung, F12 is not operational (works on other open tabs, but not this one).
msedge.exe --disable-renderer-accessibility had no effect.
Edgecrash did auto upload I see (upload ID d20b808e-73fc-4297-a845-b8a2aa0c2fd6)
- Eric_Lawrence
Microsoft
Woody Woodman (WOODY) - The 612857738 value indicates that the browser has Accessibility Mode turned on because you've got the Text Cursor Indicator feature enabled in Windows. This datapoint is written only once when the browser initially starts up-- it won't go higher than 1 with each page you load, for instance.
The supplied command line will turn off accessibility and prevent the crash/hang. If you don't see it working, the 99.9% likelihood issue is that there was already an msedge.exe instance running, so the command line was ignored when you launched the new one. You need to use Task Manager to ensure all msedge.exe instances are closed. You can then verify in your new browser instance that the edge://histograms/UIA that Accessibility Mode is no longer getting enabled by UIA, and your hangs will go away.
