Tag: Chrome 57

Chrome for Android Update Brings Crash Fixes to Users

Chrome for Android has a small update rolling out for users of the browser.  The update remains in the Chrome 57 train, with the version number updated to 57.0.2987.126.  The update is a minor one and mainly focuses on addressing a crash issue that some users were experiencing.  If you have been experiencing stability issues with the browser on your Android device, this update hopefully will address those issues for you.

In addition, the Chrome team indicated in the release notes that some improvements around CSS and performance regressions are in this update with the crash fix.

Chrome 57 Brings Improvements in Background Tab Power Consumption

Google has announced that the latest version of Chrome for Windows, Mac and Linux has a new CPU consumption throttle that will limit the power consumption of background tabs in the browser.  This new throttling policy should shows improvements to users in the form of prolonged battery life, something that Chrome and other browsers are known to impact.

The update is a change from the current timer model that is used in Chrome today.  That timer limits the refreshing of background tabs to once per second.  In this new timer, it is based on CPU consumption.  Build 57 will delay timers to the limit average of CPU load of 1% of a core.  So think of it as an augmented and improved timer model over the once-per-second timer used today.

Google Chrome for Windows

Google Chrome for Windows

It should be noted that tabs playing audio or real-time connections (like WebRTC) won’t be impacted.

So what does this really mean for end users?  It should result in improved battery life.  With fewer timer updates happening in the background, you should see battery life improvement.  How much is going to be dependent on how many background tabs you have open at any given time.  Even with these improvements, it is recommended that you keep tabs to a minimum as you work throughout the day, especially if you are running your laptop on battery power.

Eventually the Chrome team wants to get tabs fully suspended in the background and leverage new APIs to bring them back to life when you need them.  That’s still a bit away but is the end goal for the team.

 

%d bloggers like this: