#Tab suspender extension for chrome mac#

Tabs in the background that I'm not actively using have been suspended, saving on memory. Great Suspender maintains each tab's title and favicon, showing suspended tabs in a dimmed state, making it straight-forward to navigate back to them any time.

Similar to tab discarding, tabs can be un-suspended when you need to interact with them again. The Great Suspender aims to reduce Chrome's memory and GPU footprint by suspending tabs after a custom period of inactivity. If tab discarding sounds familiar, it's because you've probably come across useful Chrome extensions that give you a slightly simpler version of this idea, such as the The Great Suspender.

# Inspiration: hey there, great suspender

#Tab suspender extension for chrome mac#

We've enabled the tab discarding experiment in Chrome Canary for Windows and Mac OS, with a Linux implementation coming soon. Internal pages like new tab page, bookmarks, etc.Tab discarding discards tabs in this order: A discarded tab will display with a prefix. You can also discard a particular tab from the list by clicking its corresponding 'Discard' button.

This will discard the last tab in the list. To test out the feature, you can either carry out your normal browsing behavior until your system is in a low-memory mode, or alternatively trigger a tab discard from about:discards by clicking 'Discard tab now'. You can control whether it's enabled or disabled via the same Chrome chrome://flags page.Ī new page called chrome://discards lets you list what tabs are currently open and we try to share some insight into how interesting (we think) they are to you, from most to least. You can try out tab discarding today by enabling it via chrome://flags/#enable-tab-discarding and relaunching Chrome. To enable page reloading from cache, you can try out another experiment under chrome://flags/#show-saved-copy. When the tab is reactivated we offer you the choice to reload the cached version that was previously loaded over the network. We also have another new feature that allows caching all tab resources locally which works nicely with tab discarding when you're offline. When the tab gets reactivated we go back to the network and load it like normal. The current mechanism is similar to how we tackle tab discarding on ChromeOS. Form content, scroll position and so on are saved and restored the same way they would be during forward/backward tab navigation. If you navigate back to a tab that's been discarded, it'll reload when clicked. We kill it but it's still visible on the Chrome tab strip. What do we mean by discarding? Well, a discarded tab doesn't go anywhere. Tab discarding allows Chrome to automatically discard tabs that aren't of great interest to you when it's detected that system memory is running pretty low. That's where tab discarding can help reduce our memory usage. If I look at what tabs are consuming my system memory in the Chrome Task Manager, I'm really just 'using' one or two of the sites below whilst the other tabs in the background are unused. One of our goals is to reduce the memory used on tabs you're not actually using. This can get a little unwieldy over time. If you've got 10 tabs open there's at least 450MB of memory being spent just to keep your background tab state. # Backgroundįor every tab you have open our renderer process usually takes around 50MB per tab, even though most people use just a single tab at a time. Tab discarding is available as an experiment in Chrome 46 and above. One of our next experiments in memory use is aimed at tab hoarders (like myself). We've already seen up to a 45% reduction in GMail's memory usage thanks to improvements in V8's garbage collection process but we're really just getting started. Reducing Chrome's memory footprint is one of the team's top priorities this year.