Chrome doesn’t attempt to sandbox CPU consumption. I just closed an inactive Google docs spreadsheet, and saw CPU fall from pegged-at-100% to bubbling along at 10%.
Does it really need each available CPU cycle to wait for the other end to do something? Apparently so, in the way it’s coded.
Google: not as clever as the press release makes out.