Chrome tests “discarding” background tabs to save memory

0
543

How many tabs do you have open right now? I’m currently writing and researching this article, writing and researching another, longer article, listening to SoundCloud, and monitoring Ars chat, TweetDeck, and Parsely—so I’ve got 71 tabs open across my six monitors  taking up 10GB of RAM. (I admit that I’m probably on the upper end of things.) I’m not  using  all of those tabs right now, but I do need them open—open tabs are my to-do list. The problem is that Chrome keeps all of these tabs up and running at 100% whether I’m using them or not. This is bad for memory usage and—if you’re running on a laptop—power usage. A new feature being tested in the nightly “Canary” version of Chrome seems like a boon for heavy tab users like me: it will “discard” tabs that aren’t being used when it encounters a low-memory situation. “Discarding” a tab doesn’t mean forcibly closing a tab, just suspending it and unloading it from memory. The tab itself would still be visible in the tab bar, but unloading it would save your computer the work of keeping it running. The feature has existed in Chrome OS for some time, but now it’s moving over to Windows and Mac OS, with a Linux implementation coming soon. Chrome has a tab ranking system, and it would automatically suspend your “least interesting” tabs when it hits a low-memory situation. A Chromium.org page lists the ranking system for tabs: Read 3 remaining paragraphs | Comments

Read More:
Chrome tests “discarding” background tabs to save memory

LEAVE A REPLY

Please enter your comment!
Please enter your name here

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.