Put simply, Chrome will now limit background tabs to an average CPU load of one percent on a single core, according to a report from Ars Technica. However, there is actually a little more nuance to the way the browser will prevent background tabs from utilizing more than their fair share of system resources.
After 10 seconds of being in the background, each individual tab will be limited to a budget of CPU usage, measured in the seconds of real-world time taken to complete a particular process. Tabs are only able to use the CPU if there is time left in its budget, which regenerates at a rate of 0.01 seconds every second.
There are some exceptions, like tabs that are streaming music or video content, and tabs that are maintaining a connection to a remote server. Google also noted that the CPU budget regeneration rate might be increased, depending on feedback to the changes made as of version 57.
This is just one stage of Google’s ongoing effort to make drastic changes to the behavior of background tabs in Chrome. The company hopes to be able to achieve complete background tab suspension by 2020.
As you might expect, Google has another solution in mind to solve the problem of resource-hungry background tabs. It’s pushing a web technology called Service Workers, which aims to enhance the next generation of websites with enhanced functionality, and a better capacity to use system resources economically.
Chrome users can download the new version of the browser by opening the Settings menu and navigating to the About section.
Editors' Recommendations
- Google Chrome gets one of Microsoft Edge’s best features
- Google could finally address this huge frustration with Chrome tabs
- How to enable group tabs in Google Chrome
- Google Chrome’s new Tab Groups will bring some order to your tab chaos
- Managing dozens of tabs on Google Chrome is about to get way easier
