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.<p>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.<p>Also added an FAQ that addresses some of the low hanging fruit that I missed before: <a href="https://chromeisbad.com/#faq" rel="nofollow">https://chromeisbad.com/#faq</a>