Very useful. It'd be nice to be able to exclude certain tabs from ever being closed (like gmail) that I want to keep open.
Show HN: Save Memory in Google Chrome
271–280 of 298 posts
Re: Show HN: Save Memory in Google Chrome
#272Earlier quoted context omitted.
If hogging lots of RAM makes my program legitimately run better, then that's what it should do! Chrome runs a process per domain (or something like that) for security and stability reasons. That adds a lot of overhead for lots of tabs. But that's OK because there's actually a reason for using all that RAM.
>If hogging lots of RAM makes my program legitimately run better It objectively doesn't make your program run better to waste RAM. If RAM usage goes up 2x every two years but RAM and hard drive speed go up 20% in the same time period, then using more RAM when you don't need it is making programs more sluggish to start and to suspend to disk, and it's making computers draw more power while sleeping (to keep that much…
Objectively? That's a dangerous word; I hope you've got a better argument than this one. Hard drives are being rapidly replaced by SSDs, so their speed just jumped _way_ up (especially start-up and random access times, which affect sleeping and waking performance). 2 or 3 orders of magnitude, not 20%.
Re: Show HN: Save Memory in Google Chrome
#273Earlier quoted context omitted.
>If you have to replace that every $2 years, are you really complaining about the cost of $25 per year on your $1,000 computer system? That's assuming you're using a computer with user upgradeable RAM, and not a new macbook pro.
If it's not upgradeable then it's disposable. Get the new one next time.
You say that as if MBPs have no resale value.
The ram upgrade procedure for the new MBPs is backup, Craigslist, Apple Store, restore.
Re: Show HN: Save Memory in Google Chrome
#274Chrome used to have an option called --single-process which reduce the RAM cost to few megs.
Re: Show HN: Save Memory in Google Chrome
#275Earlier quoted context omitted.
no. when number of open tabs < 10-20, yes sure, but when that number reaches 100, your doing it all wrong. Its not about how much memory it consumes, that's irrelevant, if you need more memory just go to crucial.com, it's dirt cheap. Its about using the tools properly.
I can't argue the position for this workflow better than I already have. I refute the idea that I'm "doing it all wrong". No, I'm not and this was the only efficient way to get what I needed to do done. My laptop's motherboard can't handle more than 8GB, so I don't even have the option of putting more RAM in it as it already has 8GB. Also, I shouldn't have to keep throwing in memory to handle applications whose coder…
It wasn't the only efficient way to get what you were doing done. It's ridiculous to say that a hundred tabs is a reasonable use case. The very fact that you ran out of memory tells you that. If you really need 100 concurrent tabs (which you don't) then you need a different computer for your research. However, you're using the browser incorrectly. Why not save the text you want to a document, or out it into a spreadsheet?
10 tabs yes, 100 tabs no!! Stop arguing, even your computer's telling you the same thing :) you're just bent belligerent snd acting like a spoiler child. You're browser can't do, so you maybe should find a different way. As I've suggested.
Re: Show HN: Save Memory in Google Chrome
#276Earlier quoted context omitted.
I have 8gb. There was a time when 1gb was more than enough. Now you're saying I should have 16gb -- and you're right! This is Not A Good Thing. This is people throwing every last feature -- even if it has a pile of 800kb of DLLs/SOs attached -- into every app, with no regard for memory. I find my system thrashing almost daily at this point. I need to upgrade. Two years ago, running predominantly the same software, 4G…
Python and Ruby are on average about 40x slower than C. Fifteen years ago, this relegated them to the status of "scripting languages" that were unsuitable for Real Work. Today, there are still plenty of important applications where every clock cycle matters, but many more where that performance difference is absolutely irrelevant. We have come to understand that developer time is vastly more valuable than computing r…
Except when you're wasting that much ram you don't have room for modern high-resolution bitmaps. Binaries and GUIs and whatnot can afford to be bloated, but not everything.
Re: Show HN: Save Memory in Google Chrome
#277I'd rather waste memory than waste network traffic, re-authenticating and hitting servers to check for updated data and restarting audio/video streams.
It makes sense if you are using a machine with limited memory or you want to leave one page open whilst doing something memory intensive, but it by no means is a 'useful' way to casually browse.
Re: Show HN: Save Memory in Google Chrome
#278My big problem with Chrome tabs is that over time, they start consuming all of my CPU resources and I have to go in and kill a bunch of 'Chrome Renderer' processes to get the load back down to a reasonable level.
This also happens if Chrome crashes / I quit or force-quit out of Chrome and then restart. I don't really want it to open however many tabs I had open, I just want to be able to see what tabs were open. I would be happy with it creating the tabs with the title at the top but not loading it. Short of that, One-Tab is a decent way to help with this issue.
Re: Show HN: Save Memory in Google Chrome
#279OneTab developer here: thanks for all your suggestions, I'll be working on them :) A few FAQs: 1. The OneTab tab persists even if you close your web browser. 2. If you ever close your OneTab tab, this doesn't lose your tabs. You can always get it back by clicking the blue extension icon. 3. Your tabs are never sent to our servers unless you press the button to 'share as a web page'.
Just found a bug.
Opening a new tab by holding Control instead of right click->new tab opens the page, decreases the tab count in that group, but leaves the entry on the page. Fixed with a refresh.
Re: Show HN: Save Memory in Google Chrome
#280Earlier quoted context omitted.
Same error happening here along with a Butter bar stating "Manifest file is invalid." in Mac OS X 10.8.2 and Chrome 25.0.1364.160.
We've been looking at this, apparently this happens when an extension has just been released and is "propagating between servers". If the extension install is not working for you, it should start working later today once Google's webstore servers have updated
I've tried several times now and I'm still getting "Manifest file is invalid".