aeeble

account_circleAcceso

Chrome is Bad: Uncovering Google Chrome's Performance Issues on Mac

2025-09-12

For Mac users frustrated with sluggish performance, Google Chrome's updater, Keystone, may be the culprit. The website Chrome is Bad details how Chrome's background processes can cause massive CPU usage, slowing down computers even when the browser isn't running. By deleting Chrome and associated files, users have reported significant improvements in system performance.

The Problem with Chrome and Keystone

Chrome's auto-update feature, Keystone, has been linked to high CPU usage by the WindowServer process, a system process that manages the graphical user interface. This issue persists across restarts and affects both new and older Mac models.

Removing Chrome and Keystone

To address this issue, users can follow these steps:

  1. Delete Google Chrome from the Applications folder.
  2. Remove associated Google files from /Library and ~/Library folders, including LaunchAgents, LaunchDaemons, Application Support, Caches, and Preferences.
  3. Empty the Trash and restart the computer.

Alternative Browsers

For those looking for Chrome alternatives, Safari, Orion, Brave, Opera, and Vivaldi are recommended. Brave and Vivaldi use the Sparkle update framework, which is considered more efficient and less intrusive than Keystone.

Key Takeaways

  • Google Chrome's Keystone updater can cause significant performance issues on Macs.
  • Removing Chrome and associated files can resolve these issues.
  • Alternative browsers offer different update mechanisms that may be more efficient.
Imágenes
Calificaciones
Listas relacionadas
Comentarios