Chrome is really starting to suck these days

unnamed

When I switched from Firefox to Chrome about six years ago it was like a breath of fresh air. It was clean, super lightweight, and most importantly it was fast, really fast. I had never seen Javascript render so fast. Those days are long since gone. Google has fallen victim to its own success. Google keeps adding more and more features and the browser keeps getting heavier and slower.

Plugins generally are heavy weight and slow. A few still retain much goodness. After the terrific plugin YouTube Options shot themselves in the head by charging a ridiculous monthly fee a new one emerged called Magic Actions for YouTube. It is a super useful plugin and I like it except for one thing. They decided upon the super-idiotic route that flash control panel took; you change options from a live web site. They do this for several reasons. It allows them to advertise more easily and they can more obnoxiously beg for money. Fortunately I only have to go there a once or twice a month to change things. The other annoyance is they add a toolbar beneath the youtube window which I never ever have had a reason to use and they refuse to let you disable it. Like I can’t remember I am using your plugin? Oh that’s right you put it there for more subscriptions to your YouTube channel. Shameless.

These are my must have plugins:

Screen Shot 2015-02-15 at 2.49.52 PM

Youtube switched from Flash video as default to HTML5 as default. This is one more welcome nail in the Flash coffin. However, we lost video larger than 2k (1080p) and WebM container format via the VP9 codec does not look as good. It looks good but the difference is noticeable. Sorensen Spark is superior. This is coming from a tried and true Flash hater. I can rant about browser plugins forever.

But I digress … Chrome consumes gobs of memory. This is a screen shot of the memory usage after running Chrome for five minutes.

Screen Shot 2015-02-15 at 2.54.49 PM

As you can see Chrome is using a ton of memory. This is absurd. I also see millions of there error messages in my logs:

kernel[0]: Google Chrome He (map: 0xffffff80bb8b21e0) triggered DYLD shared region unnest for map: 0xffffff80bb8b21e0, region 0x7fff94e00000->0x7fff95000000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

I had to finally resort to disable the error reporting as my logs became useless:

$ sudo sysctl -w vm.shared_region_unnest_logging=0

Google, please fix this crap. Your features deployment have overtaken your stability. I really don’t want to have to switch back to Firefox. I really don’t.

RAM

Leave a Reply

Your email address will not be published. Required fields are marked *