Slashdot Mirror


Chrome 57 Limits Background Tabs Usage To 1% Per CPU Core (bleepingcomputer.com)

An anonymous reader quotes a report from BleepingComputer: Starting with Chrome 57, released last week, Google has put a muzzle on the amount of resources background tabs can use. According to Google engineers, Chrome 57 will temporarily delay a background tab's JavaScript timers if that tab is using more than 1% of a CPU core. Further, all background timers are suspended automatically after five minutes on mobile devices. The delay/suspension will halt resource consumption and cut down on battery usage, something that laptop, tablet, and smartphone owners can all relate. Google hinted in late January that it would limit JavaScript timers in background tabs, but nobody expected it to happen as soon as last week's Chrome release. By 2020, Google hopes to pause JavaScript operations in all background pages.

4 of 154 comments (clear)

  1. Re:Firefox already there by ChromeAeonium · · Score: 1, Funny

    True, but in Firefox's case, it is one CPU core per 1%.

  2. If this saves battery power... by viperidaenz · · Score: 4, Funny

    Is Microsoft going to stop spamming me with notifications to use Edge on my laptop because my battery will last 30% longer when ever I open Chrome?

  3. I Like This Change by TranquilVoid · · Score: 5, Funny

    A step in the right direction. Next they'll be limiting chome.exe processes to only 80% of installed RAM!

  4. Re:Blame yourselves.... by Anonymous Coward · · Score: 5, Funny

    "more add revenue"

    Surely at least one of those words is redundant. Add means addition or additional, so "more additional" is a strange thing to say. just "more revenue" or "additional revenue" would be sufficient.

    Or maybe you should just fucking learn that the abbreviation for "ADvertisement" is "ad" with one fucking d, dipshit.