Maybe Google could come up with a zero-cost tab and have users pick it (more than 10 tabs?) when they don't care about latency and pre-loading of webpages so much.
The Great Suspender: Free up memory by suspending inactive Chrome tabs
81–90 of 94 posts
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#82Earlier quoted context omitted.
Hmm. Maybe it's a FF add-on causing the problems for me, though I'm not using anything uncommon. An internal ps like chrome has might help pinning that down. Chrome is definitely the RAM greedy one (and so many processes!), and always has been.
Firefox has "about:memory", which can give you some rather detailed information about memory usage.
Chrome has chrome://memory-redirect/
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#83Earlier quoted context omitted.
Heh. First, echoing some other comments, this is a test of these web browsers. My Pale Moon instance (a Firefox fork), which I use much less "actively" and with NoScript running on it, has 42 windows with 2119 tabs, but Firefox is smart about only loading tabs on demand. On the other hand, I have to restart Palemoon regularly, to prevent it from getting unhappy I do so on every even numbered day. I also run a Firefox…
> Firefox is smart about only loading tabs on demand. This is the second time I've read this today....for me, when FF restarts, the tabs appear to be empty (they are blank, and reload when activated), but all of the memory is consumed almost as if it is somehow pre-allocated even though the page hasn't loaded. Do you not see this behavior?
Errr, I'm sorry, I have such a big memory budget on my machines that I haven't paid that close attention, I care a lot more about it hitting much my more constrained DSL Internet connection.
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#84What 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 it's like a short-term bookmarking system with a more convenient UX.
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#85Earlier quoted context omitted.
Firefox has "about:memory", which can give you some rather detailed information about memory usage.
Chrome has chrome://memory-redirect/
Strangely I can't find it in the latest dev release of chrome or chromium, it's still in stable. At least on linux, it also shows firefox's total memory usage, maybe they are doing lots of comparisons.
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#86Every single new chrome release memory consumption just gets worse. Most recently a single window with 1 gmail tab takes ~500mb (If I recall correctly you could actually run windows XP on 256). I'm seriously considering rolling my browsers back to ~2012 and never upgrading again.
What about rolling your Gmail back to 2012 with the lighter HTML version...
https://support.google.com/mail/answer/15049?hl=en
I rolled back about a month ago to free up some resources since I have it open all day. So far, so good.
As a bonus, you have to manually check for new mail, which I actually like.
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#87Earlier quoted context omitted.
There are extensions like Session Manager that list all the tabs after a crash, so you can uncheck the ones you don't want to reload. I don't know if there is one for Chrome on mobile, but it might be worth a look....
Session Buddy for non-mobile Chrome works very well and allows you to do roughly the same thing. I.e. take an saved session, maybe after copying (I think you can do that), and delete the tabs you're not interested in (it does have one level undo), and then only start the remainder, perhaps window by window (on the desktop, at least).
I love session buddy on the desktop, though with javascript off on most pages and 32gb of system memory I have yet to crash chrome from tabs there.
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#88Earlier quoted context omitted.
There are extensions like Session Manager that list all the tabs after a crash, so you can uncheck the ones you don't want to reload. I don't know if there is one for Chrome on mobile, but it might be worth a look....
Session Buddy for non-mobile Chrome works very well and allows you to do roughly the same thing. I.e. take an saved session, maybe after copying (I think you can do that), and delete the tabs you're not interested in (it does have one level undo), and then only start the remainder, perhaps window by window (on the desktop, at least).
[deleted]
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#89What 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?
Several projects underway at once, each in its own virtual desktop. Each desktop might have two or three browser windows open, each with several tabs.
As I tire of one project I switch desktop to another that's more aligned to my frame of mind.
I don't tend to kill old browser windows because they serve as a refresher to remind me where I'd got to with a certain problem, or a particular research issue. Only when I've reached some sort of resolution do I kill tabs or even whole browser windows.
Those tabs sure mount up.
Occasionally I try a different workflow but I gravitate to this habit. It seems to work for me.
Re: The Great Suspender: Free up memory by suspending inactive Chrome tabs
#90Any good alternatives recommended for Firefox?
No need. Make sure "Don't load tabs until selected" option is enabled and then restart the browser once in a while.