The Great Suspender: Free up memory by suspending inactive Chrome tabs
1–10 of 94 posts
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#2Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#3What happens when a tab is doing background work, such as uploading a file, or performing a calculation, or just keeping track of timer events? (Will those timer events appear to happen all at once when the task is resumed?)
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#4What happens when a tab is doing background work, such as uploading a file, or performing a calculation, or just keeping track of timer events? (Will those timer events appear to happen all at once when the task is resumed?)
No, there might be some service disruption with ongoing task. However, you wouldn't use it on a working tab like that, but on those residing for "I might need this later" and hogging memory.
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#5Turned that off almost immediately. Sounds good in theory, but if a suspended page has a heartbeat of any sort, it has to reload when you return to it. If that page is an infinite scroller, or if you've hit the "load more" button a couple of times, well, so much for starting up again where you left off.
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#6https://developers.google.com/web/updates/2015/09/tab-discar...
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#7Closing your tabs and using the browser's history achieves the same thing.
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#8Idea: What if there was an OS interface to mark memory regions as "throwaway"? Throwaway in the sense that it's less costly to recalculate than to recall it from swap. So the OS would throw such memory regions instead of swapping out and signal the process about it to recalculate it if needed.
I don't usually bump into heavy swap usage except when I wake my laptop from hibernate. I tend to close browsers before hibernating because it's faster to just resume the last session from a cold start then load from swap.
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#9https://developers.google.com/web/updates/2015/09/tab-discar...
Also, https://docs.google.com/document/d/1thLjq-PYoKWaM_ODDZjojr9V...
AFAIK this is part of the TRIM project in Blink, They have some memory related goals listed here:
https://docs.google.com/spreadsheets/d/17wW-YosF8tlEwn45eZ4d...
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#10Turned that off almost immediately. Sounds good in theory, but if a suspended page has a heartbeat of any sort, it has to reload when you return to it. If that page is an infinite scroller, or if you've hit the "load more" button a couple of times, well, so much for starting up again where you left off.
You can whitelist certain pages permanently which is what I do for the Twitter homepage. You can also keep them active for the current session only.