With that being said, we shall continue tracking the issue for new developments and will inform you of the same by updating this article. Nonetheless, it should roll out with an update to Chrome soon enough. This doesn’t really mean that the fix has been rolled out though, as it may have only been fixed in the Chromium base for now.
You will notice that the bug has already been marked as ‘fixed’. SourceĪs clear from above, a bug report has already been opened in the Chromium bug tracker. A Google employee recently left a comment saying that they are aware of the bug and are working on fixing it as we speak. Hence, if you do not wish to run into further issues, then there’s a piece of good news. Also, the process may simply restart itself in some time. Keep in mind though that the process is a part of Chrome and stopping it may lead to unexpected behaviors. This can be done by heading over to the Task Manager, finding the Service Worker process, and hitting the End Process button.Īs per users, this results in the CPU usage dropping back to safe utilization levels of around 10%-20%. However, there is a way to work around the problem – killing the service worker process. A screenshot of the issue (Click to enlarge) The process is also only a part of the Chrome app and the entire package may effectively keep your PC running like a cryptocurrency mining machine utilizing upwards of 70% of the CPU. That said, with the recent v.96 update, Chrome has now taken CPU usage to new heights on macOS due to the inclusion of a seemingly rogue Service Worker process that hogs over 50% of the CPU. And as more and more browsers switch to the Chromium base, there aren’t many alternatives left for users. Moreover, it’s not just Chrome that demonstrates such behavior as other browsers based on Chromium like Opera and Microsoft Edge perform similarly. The browser is notorious for being a resource-hog and causing overheating, lags, and battery drain issues. Now, Google Chrome hasn’t exactly been kind on the CPU on any machine be it Windows, macOS, or even Linux. SourceĬhrome got unusable after the update D: My computer starts heating up and the chrome process goes up to 150~200% The process has been reported to eat up a vast amount of CPU resources on many macOS machines running both the latest Big Sur update as well as the older macOS Catalina. And this has largely been due to the Google Drive service worker process. There has recently been a bunch of reports in the Google forums about the Chrome browser getting more power-hungry than ever before with a recent update. Original story (published on January 29, 2021) follows:
New updates are being added at the bottom of this story…….
0 kommentar(er)
