Did anyone ever figure out exactly what was going so wrong with Chrome resource consumption on MacOS circa 2020 and into 2021, 2022?

It seems like this isn't a problem any more but I also can't find any explanation for what was fixed to solve it. Am I missing something? (Or is it in fact still a problem?)

chromeisbad.com

@gruber it’s at the bottom of the Chrome bug report. They no longer use Keystone to update Chrome, that’s why it’s no longer happening.

Follow

@mr_mrak @gruber did anyone ever actually show a link between Keystone and high WindowServer cpu usage or even suggest a mechanism for it?

the whole thing seemed like a red herring to me, with Chrome itself, another graphical app or a macOS bug as the more likely cause...

· · Web · 2 · 0 · 0

@a @mr_mrak @gruber read the linked website. He removed it and it stopped happening. He did it on more than one Mac.

@a @mr_mrak There was definitely something going on. People seeing the problem would uninstall Chrome (including background stuff) and the problem would immediately cease.

But it also seems like the problem was fixed a few years ago.

Sign in to participate in the conversation
Amy's $30 Mastodon Instance

Just for personal use. Please click here if you're looking for my website.