Nov 19 2019 10:48 AM - edited Nov 26 2019 03:50 PM
UPDATE 2: We published 334.4 today to more broadly disable favorites sync, which should fix some sync-related crashes that users have been experiencing.
UPDATE: We published 334.3 today to fix an issue where navigation on some websites was taking an extraordinarily long time for some users. We're also hoping to publish another small revision next week to fix a couple of known crashes.
Hello insiders, today we’re releasing build 80.0.334.2 to the Dev channel! The most important thing to know this week is that, after last week’s sync issues, we’ve temporarily disabled favorites sync to prevent any more duplication. As for the other noteworthy changes:
Added features:
Improved reliability:
Changed behavior:
Known issues:
We won’t be updating next week due to the holidays, but in the meantime we’re very thankful for all your feedback and suggestions!
Nov 29 2019 12:33 AM
Nov 29 2019 12:43 AM
Nov 29 2019 04:58 AM
Nov 29 2019 02:50 PM
@RobWuijster
Myself, I have never had anything crash any Channel, BUT... I did just try to repro the scenarios you have described and I could not.; did not crash & did not close pinned tabs.
Cheers,
Drew
Dec 01 2019 03:47 AM
Dec 01 2019 06:28 PM
Dec 01 2019 07:01 PM
@steve6980
Hi Steve,
Currently, we have the 3 beta Channels, Beta, Dev & Canary. Once Edge C goes GA mid-January, obviously, that replaces Edge HTML. As for the betas, the Insider Builds, one suspicion is AN Insider (beta) Build will continue, likely as Canary. This would be similar to having regular Win10 installations whist some are, ALSO, running/testing & giving Feedback on Insider Builds... with stuff that ends up in regular installations. Some of us think there will continue to be an Insider beta & Edge may continue to evolve & develop through that, similar to the scenario with Win10.
Cheers,
Drew
Dec 01 2019 08:06 PM
@steve6980 wrote:
What will happen when beta and DEV, become the regular edge ?
There will always be Beta/Dev/Canary channels, even after stable version is released, this is just like how Google Chrome works.
Dec 01 2019 08:10 PM
"Once Edge C goes GA mid-January, obviously, that replaces Edge HTML."
Not really, only happens if you manually and intentionally install stable version on your computer. which at first will be a half-baked browser for months.
https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-sysupdate-windows-updates
Dec 02 2019 02:59 AM
Dec 02 2019 04:50 AM
@adrianghc wrote:
The way I understood it, beginning January 15 the new Edge will start to be pushed out to users automatically. If the new Edge is installed through these means, the old Edge will effectively disappear from all entry points in the UI, but it will still be there and so will the EdgeHTML engine, which is still used by UWP apps and more. I think in the long run that one will be replaced by the new engine as well but that is still some ways off - see the documentation for the new Chromium-based WebView 2:
"Developer preview is available for Win32 C++ on Windows 10, Windows 8.1, Windows 8, and Windows 7. In the future, we plan to support WebView2 on .NET, and XAML."
From https://docs.microsoft.com/en-us/microsoft-edge/hosting/webview2
Yeah the Webview was also the reason why they have been holding off the plan to roll out SETS to Windows 10, because they wanted to use the new Webview 2 based on Chromium for the SETS.
at least that's what I had read about it.
https://www.youtube.com/watch?v=3lEjuU-XFHg
Dec 02 2019 05:51 AM
@Drew1903 Hi, Thanks for checking this. I might cleanup & re-install to see if this will help.
Dec 02 2019 08:25 AM
Dec 03 2019 04:36 AM
Dec 03 2019 06:41 AM
At least for me the GPU freeze issue hasn't happened for a good week or two on Beta channel (79.0.309.40). Being stable as it is, I guess I'll keep using this build until Edge goes GA next month.
Dec 03 2019 10:25 AM
Dec 03 2019 10:25 AM
Apr 08 2020 06:14 PM
I'm also still getting this error, currently on Version 80.0.361.111.
I know this thread is a bit old, but were you ever able to find a cause/resolution?@subodhpareek18