Forum Discussion
Dev Update to 76.0.159.0 is live
Elliot Kirk Unfortunately the issue with constant high CPU/GPU load that has been present in Canary for the last few days is now in Dev. Are you aware of this and looking into it? It is impossible to use either version on a laptop now.
/ David
Also because my name is Dev and not Canary (true story). Having a browser with my name on the banner is quite fun for me :-)
- porksickleMay 21, 2019Copper Contributor
Yes, I'm having this same experience with excessive CPU and GPU usage on the macos version too. Both builds 76.0.159 and 76.0.161. It's unusable for me. Gets very hot and makes fans run.
I had been using it for a couple weeks with no issues. I had found one of the "undocumented" download links to an earlier build that had not yet been publicized and that build was great. A couple crashes, but it was fast and efficient. I notice in this current build the Windows Defender extension is installed and enabled by default. I hadn't noticed that before. Hmm...
- sambul95May 21, 2019Iron Contributor
You need to mention that builds that were NOT installed by Edge web installer, can NOT be updated or uninstalled by standard Windows means. Which build number you talk about? :)
We all hope Edge team will shortly fix this hugely important battery drainer bug.
- porksickleMay 21, 2019Copper Contributor
sambul95 wrote:You need to mention that builds that were NOT installed by Edge web installer, can NOT be updated or uninstalled by standard Windows means. Which build number you talk about? :)
We all hope Edge team will shortly fix this hugely important battery drainer bug.
The build I used previously was a build directly from Microsoft. The Verge and a couple other sites had found the URL to the Dev channel download a week or so before Microsoft communicated it, and I downloaded and used it.
When the Dev build was officially communicated from Microsoft on their website, I downloaded it again and it replaced the previous version. So I can't check what the previous version number was.
BTW I'm using the macos version, so I can just drag it to the trash and uninstall anytime I want. The reason I posted here is because the high CPU usage bug seems to exist in both the macos and Windows 10 Dev builds (I am using both on two different machines and see the behavior both places.) It appears to be a "cross platform bug". :-) .
- Drew1903May 17, 2019Silver Contributor
DevLunsford
Hey, Dev, thanks for the morning smile 😁
Cheers,
Drew