Live data from Hacker News

The Great Suspender: Free up memory by suspending inactive Chrome tabs

chrome.google.com

41–50 of 94 posts

Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs

#43
post #12

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…

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?

For me, I open a new window for each task I have to do in the morning, and the tabs associated with each one, then the inevitable stack overflow and msn pages pile up as I finish them

Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs

#44

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.

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.…

This always drives me mad. It's particularly bad if I'm trying to read content sites on a train or somewhere with patchy reception - open half a dozen tabs to give me something to read while I'm disconnected, and then switch to them only to see the content disappear before my eyes. I'd nominate it as literally the worst thing about mobile browsing

Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs

#45
I prefer to "snooze" tabs using the Tab Snooze Chrome Extension. That way they reappear when I can hopefully give them attention. I can tell the extension to put tabs to sleep until this evening, tomorrow, this weekend, next week (my fave), next month, someday (I haven't tried that one, too scary), or a specific date. https://chrome.google.com/webstore/detail/tab-snooze/pdiebia...

Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs

#46
post #12

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…

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?

It's pretty simple really.

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

#47
post #12

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…

I would recommend you try Tab Outliner[0]. It has a bit of a learning curve and adjust your workflow.

[0]: https://chrome.google.com/webstore/detail/tabs-outliner/eggk...

Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs

#48
post #12

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…

I create a folder called ReadMe. In it I dump everything I want to read later. Every month I clean it; if I haven't read it by then, it wasn't that important.

Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs

#49

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.

Only if the infinite scroll is of the sort that should not exist. User friendly solutions update the url.
Post reply on HN