Jun 09 2021 10:06 AM
Jun 09 2021 10:06 AM
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 still got lots to talk about!
Now, for this week’s notables:
Beta users, be on the lookout for version 92 to come to you soon!
Jun 10 2021 11:25 PM
Jun 10 2021 11:57 PM - edited Jun 11 2021 04:04 AM
I kind of figured out what's going on with YouTube - the page always seems to hang when it tries loading the Related Videos on the side. Even if the video itself manages to start auto-playing, those never come in, and eventually that's when the video freezes.
Lo and behold, Enhancer for YouTube has an option for that!
I ticked "Hide related videos", killed the YouTube tab process that had reached 3 GB of RAM, and now YouTube just works again lol.
Nope. Still broken.
Jun 11 2021 06:05 AM
@AlexD Going back to Beta version (if someone doesn't known, it's pretty easy: copy everyting from %userprofile%\appdata\Local\microsoft\edge dev into %userprofile%\appdata\Local\microsoft\edge beta). The current dev version is unusable....
Jun 13 2021 10:05 PM
Jun 14 2021 07:07 AM
Jun 14 2021 09:02 AM - edited Jun 14 2021 09:09 AM
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
612857738 (1 = 100.0%)
See https://www.reddit.com/r/edge/comments/nx1170/edge_crashes_on_multiple_sites_result_code_hung/h1f9je... 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
Jun 14 2021 09:10 AM
Jun 14 2021 10:32 AM
@ericlaw 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.
Jun 14 2021 11:09 AM - edited Jun 14 2021 02:13 PM
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).
Jun 14 2021 02:11 PM
Jun 14 2021 04:09 PM