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.
Web developers who write javascript that just keeps chewing up resources are why we have to resort to this.... You have no one to blame but yourselves for abusing the privilege of having active content that just sucks resources to get more add revenue....
I know some of you developers actually think about such stuff and care about the end user's experience, but there are a few of you out there that are messing stuff up for all of us, so now the browser has to throttle you.. Thank You for nothing (from the rest of us).
"File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
Because making a web app in JavaScript is cheaper than making five native apps, one each for Windows, macOS, GNU/Linux, iOS, and Android.
This feature should allow whitelisting domains to keep javascript fully active. I want my email client to keep running javascript. I don't want some random news page I left open to decide it's time to launch a video ad.
Ads and trackers