Google Chrome Became a Performance Hog

I own a single-core laptop with 1 GB of memory. Google Chrome version 34 for Linux 64 bit (ArchLinux) is completely unusable on this machine. I own another single-core laptop with 512 MB of memory. Google Chrome version 12 for 32 bit (Ubuntu 10.04) works just fine on this machine. Both machines are considered somewhat old and underpowered according todays standard. Nevertheless they should be able to browse the web at least as fast as any smartphone or tablet.

As has already been said in other posts (here and here): Newer is not better.

I checked my old downloads: I have copies of Google Chrome 64 bit Debian packages which have size 13 MB in 2010. At end of 2011 it climbed to 24 MB, in 2012 to 36 MB, in 2013 to 43 MB. Now Chrome 64 bit Debian packages are 49 MB. This tremendous increase cannot be explained by security fixes.

ChromeFatter

See Blackduck: Google Chrome for a lines-of-codes against time chart.
GoogleChromeLOC1

On that occasion I searched for alternatives which can replace Google Chrome and its memory obesity. Two possible contenders might be QupZilla and Midori. QupZilla just worked out of the box, while Midori crashed repeatedly on Ubuntu 14.04. Unfortunately I did not get Flash to work with QupZilla. i.e., no YouTube with QupZilla.

Advertisements

One thought on “Google Chrome Became a Performance Hog

  1. Pingback: No YouTube Videos on Google Chrome v50 – Elmar Klausmeier's Weblog

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s