(Update, the good people at Google on the Chromium team are taking this seriously, if you're technically inclined and can contribute samples please see this thread – direct link to the crbug 1158402.) OK that's weird, how do you delete Chrome and Keystone? Yeah, I realize this sounds like a freakin' infomercial, but it worked so well I spent a whole $5 on a domain name and set up this website even if it makes me sound like a raving nut. I deleted Chrome, and all the files Keystone had littered on the computer, restarted, and it was so snappy it felt like a brand new computer. Then I remembered, installing Chrome was always one of the first things we did when we set up the computer. We even went as far as to completely wipe and set up the computer fresh multiple times. I had tried everything I could think of – it had a Fusion drive and the symptoms were consistent with a failing SSD – but drive diagnostics always turned up nothing. Then something else hit me, my family had been complaining about the sluggish performance of a 2015 iMac since practically the day we bought it. 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. I deleted Chrome, and noticed Keystone while deleting some of Chrome's other preferences and caches. Activity Monitor showed *nothing* from Google using the CPU, but WindowServer was taking ~80%, which is abnormally high (it should use <10% normally).ĭoing all the normal things (quitting apps, logging out other users, restarting, zapping PRAM/SMC, etc) did nothing, then I remembered I had installed Chrome a while back to test a website. Long story: I noticed my brand new 16" MacBook Pro started acting sluggishly doing even trivial things like scrolling. Deleting Chrome and Keystone made my computer way, way faster, all the time. Short story: Google Chrome installs an updater called Keystone on your computer, which is bizarrely correlated to massive unexplained CPU usage in WindowServer (a system process), and made my whole computer slow even when Chrome wasn't running.
0 kommentar(er)
