The Great Suspender: Free up memory by suspending inactive Chrome tabs
41–50 of 94 posts
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#42Just curious - how are you sure that the addon doesn't have some backchannel that it's using to send your website info to? Like, let's say you go on a banking website?
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#43What 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…
I'm genuinely interested in the reasons people maintain so many tabs open. What type of workflow you have when you end up with so much stuff open? How do you get back to some of those tabs? Wouldn't it be easier to just google it again when you need it instead of having it lingering around and wasting your HW resources?
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#44Turned 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.
Mobile browsers already suspended most background stuff, and it occasionally does cause issues like that, but usually it just works. 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.…
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#45Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#46What 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…
I'm genuinely interested in the reasons people maintain so many tabs open. What type of workflow you have when you end up with so much stuff open? How do you get back to some of those tabs? Wouldn't it be easier to just google it again when you need it instead of having it lingering around and wasting your HW resources?
I have a branching factor > 1.0 which means for every tab I open, upon reading that tab, I find at least one more interesting link, and up another tab comes.
It would converge to infinity if my computer didn't crash in a manner causing chrome to be unable to reload, or I didn't periodically hit chrome bugs in the O(1000)'s tab range.
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#47What 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…
[0]: https://chrome.google.com/webstore/detail/tabs-outliner/eggk...
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#48What 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…
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#49Turned 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.