»Google Chrome and Associated Files Reportedly Harm Your Mac s Performance: Here s How to Fix It
2-MIN READ
Google Chrome and Associated Files Reportedly Harm Your Mac s Performance: Here s How to Fix It
Google Chrome on Mac
A Google Chrome user, who is also a software developer has created a Chrome is Bad website that explains the issue and tells how to make Mac computers faster by deleting Chrome and other associated files.
FOLLOW US ON:
It is a known fact that Google Chrome is one of the most excruciating web browser for a computer s processor and battery alike. Both Mac and Windows users alike have been reporting that the Google web browser has been slowing down their computers, at times even when it wasn t even open. Now, findings from one such frustrated Chrome user on Mac, who also happened to be a software developer, discovered that the reason behind Mac computers slowing down is the Chrome Keystone, which is an auto-update mechanism. In order to explain the issue, t
16 December 2020, 6:42 am EST By
Google Chrome might be the world s biggest web browser, but it s been known to slow down both Mac and Windows computers, especially affecting a system s battery and processors, with some reporting that the browser affects them even when it s not on. Chrome is Bad
Chrome has millions of active users, but the cause has been unclear for many.
That is until one frustrated Chrome user on Mac found out in his research that the reason behind the Mac slowing down is due to the Chrome Keystone, an auto-update mechanism put in place by the company.
To explain the issue further, Loren Brichter, a software developer, created the website known as Chrome is Bad, which also includes a detailed solution for the problem.
A developer claims Google Chrome may be slowing down MacBook computers
Loran Brichter created a website to explain the problem and give a solution
He claims that Chrome installs the auto-update mechanism Keystone
This updater runs in the background and is undetected by the Activity Monitor
Brichter claims uninstalling Chrome and Keystone will improve performance
However, a separate report is calling the problem and solution wild
The report conducted an experiment with and without Chrome and Keystone
It found no significant difference in the WindowServer CPU usage