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.

Comments

Audio and WebSockets defeat this

[tepples]

sometimes I'll listen to a podcast/music in a another tab

Then this does not affect you. From the featured article:

The good news is that background tabs playing audio or maintaining real-time connections like WebSockets or WebRTC won’t be affected by the 1% CPU usage limit.