And never got any satisfying answers or solutions. I even took the rare-step for me and bugged a few friends at Big Fruit. So, I tweeted out my complaints about it, about whether PDK, the plugin manager daemon was causing it, whether WindowServer itself had gone rogue or gone bad. And I just blamed macOS Catalina for it because Catalina seemed to be one of those painful transitional updates that everyone blamed for everything. Literally, up all night, watching Final Cut Pro performance plummet, wasting hours, precious hours, rebooting, uninstalling plugins, just everything imaginable. It was especially bad when I was up all night trying to finish my embargoed video reviews for the iPhones, Apple Watch, Macs, and everything else released this year. See, all year, I've been incredibly frustrated, maddened even, by similar problems and had similarly tried everything I could think of. WindowServer painġ6-inch MacBook Pro (Image credit: Rene Ritchie / iMore) Everything was instantly and noticeably faster, and WindowServer CPU was well under 10% again. I deleted everything from Google I could find, restarted the computer, and it was like night-and-day. Activity Monitor showed nothing from Google using the CPU, but WindowServer was taking ~80%, which is abnormally high (it should use <10% normally).Doing all the normal things (quitting apps, logging out other users, restarting, zapping PRAM, etc) did nothing, then I remembered I had installed Chrome a while back to test a website.I deleted Chrome, and noticed Keystone while deleting some of Chrome's other preferences and caches. I noticed my brand new 16" MacBook Pro started acting sluggishly doing even trivial things like scrolling. It also has a long history of crashing Macs.įrom Loren's website, and this part really resonated with me, and I'll tell you why in a sec:
There is no reason for auto-update software to need to do what Chrome/Keystone was doing. But either way, I'm not inclined to give Google-the-organization the benefit of the doubt (despite the many good people who work on Chrome) since it's been a decade+ and this still hasn't been "fixed". I don't know if Google was doing something nefarious with Keystone, or a third party figured out how to (which Wired warned about).
And other websites have reported on problems with it since then. But, according to Loren's theory, when that process goes wrong, it goes wrong before Keystone shows up in Activity Monitor, which makes it effectively hidden even as it's causing the problem.Īlso, that this is nothing new, that Wired called Keystone 'evil' way back in 2009 already, when it kicked off with Google Earth.
Now, it isn't that Google's background updater, Keystone, hides itself from Activity Monitor it's that it only shows up when it's actively updating Chrome.
0 kommentar(er)
