21–30 of 94 posts
https://developers.google.com/web/updates/2015/09/tab-discar...
What I do, when Chrome, or rather, my abuse of it (14 windows, 735 tabs at the moment, Ubuntu 14.04 64 bit on a 32 GiB system) becomes onerous is to go to the task manager and kill groups of tabs taking up "too much" memory, and very occasionally, too much CPU. (I get away with that abuse, which it a bit higher right now because I'm in the process of buying a house, by killing all tabs after launching, and only enabl…
Afaik, current versions of Chrome already implement the functionality of the great suspender natively.
Like others have said, The Great Suspender will often break web pages and force them to completely reload. This ruins infinite scroller pages too. So thats the trade off.
What I do, when Chrome, or rather, my abuse of it (14 windows, 735 tabs at the moment, Ubuntu 14.04 64 bit on a 32 GiB system) becomes onerous is to go to the task manager and kill groups of tabs taking up "too much" memory, and very occasionally, too much CPU. (I get away with that abuse, which it a bit higher right now because I'm in the process of buying a house, by killing all tabs after launching, and only enabl…
Ah, good, it's not just me! One anecdote - 5 years ago FF was the clear winner for coping with tab abuse. Stable and coped with hundreds of tabs happily, Chrome started crashing pages beyond 50 or so. Now it's the perfect reverse, FF hates a lot of tabs open and Chrome is stable with apparently limitless numbers.
What I do, when Chrome, or rather, my abuse of it (14 windows, 735 tabs at the moment, Ubuntu 14.04 64 bit on a 32 GiB system) becomes onerous is to go to the task manager and kill groups of tabs taking up "too much" memory, and very occasionally, too much CPU. (I get away with that abuse, which it a bit higher right now because I'm in the process of buying a house, by killing all tabs after launching, and only enabl…
Ah, good, it's not just me! One anecdote - 5 years ago FF was the clear winner for coping with tab abuse. Stable and coped with hundreds of tabs happily, Chrome started crashing pages beyond 50 or so. Now it's the perfect reverse, FF hates a lot of tabs open and Chrome is stable with apparently limitless numbers.
Turned 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.
I learned this out a few years ago when trying to figure out why my metrics sometimes reported mobile visitors with load times of hours or even days... Turns out that they opened the site and then switched tabs/apps before it finished loading. Everything except that metric worked fine. I added a heartbeat just to detect that, and it worked without introducing any extra reloads.
What I do, when Chrome, or rather, my abuse of it (14 windows, 735 tabs at the moment, Ubuntu 14.04 64 bit on a 32 GiB system) becomes onerous is to go to the task manager and kill groups of tabs taking up "too much" memory, and very occasionally, too much CPU. (I get away with that abuse, which it a bit higher right now because I'm in the process of buying a house, by killing all tabs after launching, and only enabl…
Incidentally, recent builds of the Chromium-based Vivaldi browser had this suspend feature before Chrome did. As did some Chrome extensions, of course.
Idea: 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 hiber…