Chrome doesn’t sandbox the CPU; Goggle docs waits really hard

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.

If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.

1 thought on “Chrome doesn’t sandbox the CPU; Goggle docs waits really hard

  1. PaulW

    Doesn’t do that here. How do you see sandboxing CPU working? Surely as you open more tabs the available CPU for each one would go down until tabs that need the CPU are overly restricted?

Comments are closed.