I'm gonna try this. Thank you.
Anyone who does: Please consider doing a video of the process and results, or some other proof.
It would be awesome to get traction on this, but there needs to be undeniable evidence first.
Chrome Is Bad
121–130 of 306 posts
Re: Chrome Is Bad
#122I've had noticeable issues with "WindowServer" in the past (taking 80% CPU usage and causing the fans to ramp up even when the system seemed like it should be idling even after a reboot) so I decided to give this a shot. This is anecdotal but there is a noticeable difference for me with responsiveness after following these steps. Currently the WindowServer process is hovering around 14%.
Most likely the issue was resolved by the reboot, not by uninstalling Chrome. From my experience Mac OS tends to slow down after a few days. Animations and scrolling gets choppy and there's nothing I can do to fix it, short of rebooting.
> From my experience Mac OS tends to slow down after a few days
Just for the sake of the argument, do you have installed Chrome?
Re: Chrome Is Bad
#123The author went so far as to create a domain for this rant, and yet didn't even do any performance metrics or basic forensic analysis at all. I'm not saying the author is wrong, but there's a lot of questions here. How does Keystone hide itself from the Activity Monitor? Is there a Keystone process if you run `ps aux`? Did you run dtruss/strace? What is it doing when Chrome isn't running that causes it to degrade per…
Another thing you can do: profile the process to find out what exactly it’s spending all that CPU time on. There are a few different ways to do this on macOS, including the GUI Instruments.app which comes with Xcode, and dtrace. But if you’re the sort who always has a terminal open, the quickest way is to just run sudo spindump Also useful when a process is hung, even if it’s not taking up CPU time. Sometimes the out…
So users are expected to run debugger tools in order to figure out what some hidden program is doing?
Many years back I couldn't sleep and noticed my HDD's was working hard. I checked and it was google updater that was scanning everything...
I will never know why, they might be stealing IP (i was working on OCR at the time) or they just wanted to create a profile to serve better ads...
Re: Chrome Is Bad
#124I've had noticeable issues with "WindowServer" in the past (taking 80% CPU usage and causing the fans to ramp up even when the system seemed like it should be idling even after a reboot) so I decided to give this a shot. This is anecdotal but there is a noticeable difference for me with responsiveness after following these steps. Currently the WindowServer process is hovering around 14%.
Most likely the issue was resolved by the reboot, not by uninstalling Chrome. From my experience Mac OS tends to slow down after a few days. Animations and scrolling gets choppy and there's nothing I can do to fix it, short of rebooting.
Yes. Just like Linux - in 1996.
Very sad.
(I have recently started using Apple tools for developping with Swift/Xcode on iPad. I am very unimpressed by the quality of the tools, and quite impressed by the range and depth of features....)
Re: Chrome Is Bad
#125Earlier quoted context omitted.
This is why dates on articles is so important. I can’t tell if this website is newer or older than that response so I can’t tell if this is a problem today or was a problem that was resolved
Appears website is newer - https://twitter.com/lorenb/status/1337832978253230081
Huh. Chromeisbad.com doesn't have an author credit, but the tweet implies it's by notable iOS developer Loren Brichter, creator of Tweetie, Letterpress, and inventor of pull-to-refresh.
Re: Chrome Is Bad
#126The window to the internet should not be some monster that takes millions of developer hours and held ransom by a couple of big companies. I should be able to build my own browser in a 3 month sabbatical.
The Internet is much bigger than the Interweb.
Re: Chrome Is Bad
#127I've had noticeable issues with "WindowServer" in the past (taking 80% CPU usage and causing the fans to ramp up even when the system seemed like it should be idling even after a reboot) so I decided to give this a shot. This is anecdotal but there is a noticeable difference for me with responsiveness after following these steps. Currently the WindowServer process is hovering around 14%.
Most likely the issue was resolved by the reboot, not by uninstalling Chrome. From my experience Mac OS tends to slow down after a few days. Animations and scrolling gets choppy and there's nothing I can do to fix it, short of rebooting.
I can assure you that it wasn't related just to rebooting as this has been something that's been bugging me for months. I had previously rebooted earlier in the day because of this exact same issue (a runaway WindowServer process), before I saw this article. I also did a fresh reboot before following these instructions too as a sort of "control".
The change only happened for me after removing Chrome as well as the launch agent for keystone.
Re: Chrome Is Bad
#128Should be called "Keystone, part of Chrome, appears to behave badly on my Mac." There's nothing like this running on my Linux box.