Google needs to release a completely stripped down Chrome. Not a memory hog, very lightweight, fast.

I don't care if I can't add extensions or apps; I miss when Chrome was faster and more lightweight. If Google wants to keep increasing Chrome's memory usage that's fine but they should also release a version with none of that bloatware. I switched back to Firefox because it takes less memory and doesn't slow my computer down as much.

15 thoughts on “Google needs to release a completely stripped down Chrome. Not a memory hog, very lightweight, fast.”

  1. I don’t think there’s much difference in resource consumption between having no extension installed and having no extension infrastructure. I doubt you will make Chrome faster just by removing that.

    You would have to remove many other features, till it’s basically no different from other lightweight Webkit alternatives. Just use one of those already. Have a look to [Midori]( or [Xombrero](

  2. Chrome is not a browser, chrome is a platform. It’s like Java at this point – only secure.

    I personally like the way it’s going – but I can understand that people sometimes just want a simple lightweight browser………but that’s not chrome

  3. My experience with Chrome is fantastic. People who want a lightweight Chrome would still bitch so I do not think Google should waste their time trying to please the un-pleasable.

  4. The Chrome developers blame the extensions, and the extension devs blame Chrome, but I don’t care…

    I run a large VM cluster for office desktop VMs, and the moment something more efficient comes around, I’m moving everyone’s default browser over to that.

  5. I have over 10 extensions, running 300 tabs with 8GB on a laptop and chrome still runs fast enough without any annoying slowdowns

    You need to optimize your install and delete old files OP….

  6. To those people, who thinks that Chrome is a memory hog, I recommend reading **[how memory works in Chromium](**.

    > **Weaknesses of a Multi-Process Model on Memory Usage**

    > Using a multi-process model within the browser offers benefits for reliability, robustness, and security of the browser. Those benefits drove our design toward the multi-process model, and you can read more about them here.
    > However, using multiple processes is somewhat at odds with building a lightweight browser. First off, each process does have some amount of overhead. The process overhead turns out to be relatively small, however, once you’ve accounted for the shared memory properly. The more significant handicaps are the replicated internal components of a browser, such as caches, JavaScript VM heaps, and internal data structures which must be duplicated inside multiple processes. JavaScript is particularly troublesome because of its garbage collected heap. Heaps are generally relatively large and must be replicated across each browser process.
    > How can Chromium overcome these deficiencies? In short, it can’t 🙂 All we can do is to make everything else that much smaller, so that the effects of being multi-process is minimized. As a result, there are degenerate cases where Chromium uses a lot more RAM than other browsers. The case which is worst is where many tabs are open, each to separate domains with large amounts of JavaScript. But for typical usage, we think Chromium fares well at balancing the benefits of multiple processes and also maintaining memory usage at levels which is lower than some popular browsers.

  7. This thread has been linked to from another place on reddit.

    – [/r/mistyfront] [Google needs to release a completely stripped down Chrome. Not a memory hog, very lightweight, fast. (/r/chrome)](

    *^If ^you ^follow ^any ^of ^the ^above ^links, ^respect ^the ^rules ^of ^reddit ^and ^don’t ^vote. ^\([Info](/r/TotesMessenger/wiki/) ^/ ^[Contact](/message/compose/?to=\/r\/TotesMessenger))* [](#bot)


Leave a Comment