lorenb

Noticed that my original rage post (sorry about that) got submitted here and was justifiably flagged. Now the Chromium team is looking for some pretty detailed info to help track down the issue of suspiciously high WindowServer CPU usage potentially caused by the way Chrome/Keystone interacts with the system.

This is the right crowd to ask since not many people can follow the instructions. If you have noticed high WindowServer CPU and haven’t yet tried deleting Chrome/Keystone, please check out the bug.

Also added an FAQ that addresses some of the low hanging fruit that I missed before: https://chromeisbad.com/#faq

I didn't submit it or write it for this crowd.

WindowServer CPU before/after is as objective as I've got. I'm convinced there's a fire, but I can only show you the smoke: https://twitter.com/lorenb/timelines/1338892756752732169

For those that didn't measure, it's almost irrelevant — I'm telling you it's not a subtle difference. It's night-and-day.

It's very low on my list of plausible theories, but if there was a hypothetical keystone exploit, what is the latest on code-injecting WindowServer?

Also added an FAQ to the site: https://chromeisbad.com/#faq to address the low-hanging fruit of obvious objections to the possibility that Chrome/keystone is doing something to the system to cause it to thrash.

try `mdfind keystone` in terminal

This is a fair comment.

At the same time even "hard" evidence would likely get dismissed as anecdotal, and there's certainly enough of it now (and even plenty in the past) to point a clear finger at Chrome/Keystone.

This certainly beat filing it in the black hole that is Chromium's bug reporter where it would have been ignored / works-on-my-machine'd / or dismissed as anecdotal there.

Whatever it is doing is sketchy and causing WindowServer to thrash. And this is not the first sketchy thing it has done.

Yeah, it felt weird to put my name on it, people usually do that when they have something to sell. Someone mentioned that it seems sketchy being anonymous so I'll probably sign it.

There's no upside for me either way.

Yeah, there was no super master plan here, just that after dealing with one sluggish computer for days (you name it, I tried it), and another one for 5 years... the fact that it turned out to be slow because of an app that wasn't even running was pretty frustrating.

Filing a bug report that would get "works on my machine"'d and then ignored and auto-closed by a bot in 5 years didn't quite feel worthy.

Auto-updating browsers are a good idea. Keystone is bad auto-updating software. It should probably get scrapped.

Nope

> If the corner-cutting that led to 737 Max problems is to be understood as a "greed" move, it's a pretty incompetent one, because Boeing is almost certainly out billions over the mess.

Incompetence and greed aren’t mutually exclusive.

If you take the word of all of the good engineers who were pushed out or quit in frustration over the financialization of the company after the McDonnall Douglas merger, then “omg greed” really does explain everything.

Note that this could have been (and was) predicted by anyone with half a brain:

“On some level, though, he saw it all coming; he even demonstrated how the costs of a grounded plane would dwarf the short-term savings achieved from the latest outsourcing binge in one of his reports that no one read back in 2002.*“

https://newrepublic.com/article/154944/boeing-737-max-invest...

You’re thinking of I-joists, which are a kind of engineered lumber, not a kind of mass timber. And those do light up like kindling. The glue used in glulams and the like chars at the same rate as the wood, and it’s pretty easy to achieve known fire ratings simply by making the members a little chunkier than they need to be since the char rate is known.