Oct 08 2019 11:32 AM
Hello insiders, today we’re releasing build 79.0.294.1 to the Dev Channel! It’s a pretty normal week this week, so you can see the most noteworthy changes below:
Added Features:
Improved Reliability:
Improved Behavior:
As always, we thank you for using Edge, and for sending us all your great feedback and suggestions!
Oct 09 2019 06:51 PM
@Spaceball_Seven
That's rather odd, but, try using THIS.
Cheers,
Drew
Oct 09 2019 07:34 PM
Oct 10 2019 01:16 AM
@Spaceball_Seven wrote:I can't use the smiley face icon or menu to Send Feedback. Clicking on either will crash Edge.
That's really bad, try reinstalling the browser and during uninstall, when asked, choose to remove all data along with it.
because for these kinds of technical problems, a simple form is no good. the smiley button allows you to send Additional data to help them identify and fix the problem and also what is going on in your system while the CPU usage spike occurs.
Oct 10 2019 01:51 AM
Great work on the recent builds Team!
I'm noticing some high CPU usage in the latest build on Mac - my workstation was updated to Catalina last night so not sure if that has anything to do with it.
Also, are there any plans for a dedicated "Check for updates" button on PC like there is in Mac's "Help" menu? Having to go into Help & Feedback > About Edge for manual update checking is quite tedious.
Looking forward to future builds! :)
Oct 10 2019 03:09 AM
@CIMarketingVideo
I'll stick my nose in & say something about the updating for you. Presently, we are updating beta builds, previews, test rats, call the Edge C Channels whatever, but... once with a non-beta, non-Insider Build, it will not be manual or frequent updating. Will be similar to Edge being kept up to date; it will be Edge being kept up to date (wink). Consider, currently, there are 3 (different) Channels and 3 (different) rates of updating; that's no norm in daily practice with an entrenched browser which, Edge C isn't, yet. It's a work in progress, now and won't be manually updating after it's done & kicked out the door.
Cheers,
Drew
Oct 10 2019 03:14 AM
@CIMarketingVideo wrote:
Great work on the recent builds Team!
I'm noticing some high CPU usage in the latest build on Mac - my workstation was updated to Catalina last night so not sure if that has anything to do with it.
Also, are there any plans for a dedicated "Check for updates" button on PC like there is in Mac's "Help" menu? Having to go into Help & Feedback > About Edge for manual update checking is quite tedious.
Looking forward to future builds! :)
I'd like a dedicated update button as well. the current system is taken from Google chrome without any changes. in the past Microsoft relied on Windows update to ship updates to their browsers (IE and Edge classic), so they should create a new system for the new Edge too, like you said a dedicated button for update.
I also think they should add a setting in GP to let us change the frequency of the auto update checking cycle. like set it to every 30 mins, 1 hour or 24 hrs.
of course the shorter durations are better for Canary.
Oct 10 2019 03:20 AM
@Drew1903 wrote:@CIMarketingVideo
I'll stick my nose in & say something about the updating for you. Presently, we are updating beta builds, previews, test rats, call the Edge C Channels whatever, but... once with a non-beta, non-Insider Build, it will not be manual or frequent updating. Will be similar to Edge being kept up to date; it will be Edge being kept up to date (wink). Consider, currently, there are 3 (different) Channels and 3 (different) rates of updating; that's no norm in daily practice with an entrenched browser which, Edge C isn't, yet. It's a work in progress, now and won't be manually updating after it's done & kicked out the door.
Even when the stable version of Edge will be released, that doesn't stop Beta/Dev/Canary users.
google chrome stable is released but there are still huge number of beta/dev/canary testers for the browse, they range from enthusiasts to developers and anyone in between.
most of us are used to more regular updates and I believe a good amount of people will want to still have faster and sooner access to the new features in Edge insider so they'd keep a Dev/Beta/Canary version beside the Stable version.
so my point is, a dedicated update button and an ability to set update cycle for Edge insider is a good idea. google chrome is missing this feature and it makes it double important for Edge to implement it as an advantage.
Oct 10 2019 10:52 AM
@HotCakeX "I'd like a dedicated update button as well."
What exactly do you mean by this? You want to be able to request it or do you want to be able to stop it?
I only ask because, like Chrome itself, if you go to the About Microsoft Edge menu item, it will check for the most recent update and download if there is one. It's the default action in Chrome and I assume it is in Edge as well.
Oct 10 2019 11:44 AM
Oct 10 2019 07:12 PM
@josh_bodner I see others are reporting high CPU utilization on this build in macOS Catalina. I'm experiencing the same thing and it's with static pages. At one point I saw my CPU utilization by Edge get near or exceed 500%. I'm unclear the cause since it seems to just increase over time and I'm looking at largely static pages, downloading files, and not watching video/listening to audio from the browser.
Oct 11 2019 12:08 AM
@lindhartsen wrote:@josh_bodner I see others are reporting high CPU utilization on this build in macOS Catalina. I'm experiencing the same thing and it's with static pages. At one point I saw my CPU utilization by Edge get near or exceed 500%. I'm unclear the cause since it seems to just increase over time and I'm looking at largely static pages, downloading files, and not watching video/listening to audio from the browser.
Hi,
try disabling "Microsoft Defender SmartScreen" from the Edge insider settings
some people reported doing that will fix the issue as a workaround
Oct 11 2019 09:21 AM
Oct 11 2019 09:29 AM
Oct 11 2019 04:40 PM
@lindhartsen and in case anybody else is still seeing high CPU usage, we had quite a few separate bugs this week that caused higher CPU usage, and we got a couple of fixes for some of them into today's Canary (301) that should also help.
Oct 11 2019 11:58 PM
Oct 14 2019 02:09 PM
@josh_bodner So after updating today, I basically get this
I've tried uninstalling, re-installing, restarting the machine, updating windows and nothing works. I'm at a loss here.
Oct 14 2019 02:18 PM