I’ve had continual issues with Firefox on all my systems. It hogs CPU cycles and RAM like there’s no tomorrow. It crashes often when viewing Flash intensive pages such as Grooveshark and Photobucket. I’m almost missing Internet Exploder these days. 😉
Seriously, I’ve tried all the usual remedies: running FF in Safe Mode, checking/removing extensions, using up-to-date plugins, nuking it all and starting with a fresh profile, etc. Nothing seems to solve the issue. Even with the new profile, FF managed to begin its old (mis)behaviors within days. It’s frustrating. It was beginning to take the joy out of the Internet for me.
In a previous article here, I mention trying Pale Moon as a remedy to my FF problems. That went fine for a bit, but eventually Pale Moon began to display the hogging tendencies of FF. This is not to say that PM was the issue. It was most definitely the underlying FF browser functions that were causing these same issues in PM.
I’ve tried Webkit-based browsers like Midori. They’re fast, lean, and not at all greedy with resources; however, they’re also rather plain when it comes to features and customization potential. I like my FF. I like the way I had it set up. Unfortunately, the sleekest, coolest, most awesome hot rod car is nothing if it doesn’t run well enough to drive to the little store up the street for a pack of smokes. 😦
I’ve had many folks jump up and down and recommend Chrome/Chromium to me. Well, I wasn’t going to compile the branded Google Chrome for my Slackware system for two reasons: it required too many dependencies that I didn’t want to have to search for/compile/install, and I don’t particularly care to be sucked (assimilated) into the Google Collective at this time.
So, what I did was grab a Chromium .txz package that had been compiled by dedicated Slackware friend, Alien Bob (Eric Hameleers), to whom I still owe a big donation one of these days. You’ll actually find the link to Eric’s Chromium build on Google Chrome’s download site under “community supported versions” download link. Anyway, downloaded and installed. Now the fun begins.
I had to first off find compatible extensions for Chromium that were at least functionally similar to the primary ones I use in FF. That wasn’t a major problem. There are loads of extensions available at the Google Chrome Web Store. I found ad blocking, flash blocking, script blocking, and other security and special function extensions there. So, I’m all set there.
One thing that I couldn’t find was a decent version of Speed Dial for Chromium. The ones that were advertised as equivalent to the FF Speed Dial were far from being the same. I worked around this by creating my own custom dial page(s) that I serve on my locally. I do the same for my custom home pages, so that all worked out fine.
My Chromium w/ custom dial page
My next BIG issue with Chromium was the fact that it SUCKS at rendering fonts. I’m used to those crisp, clean fonts in FF. Not so in Chromium. They’re ugly. I tried some of the extensions out there that are meant to improve the fonts, but none are actually for Linux, so they didn’t really have any effect. While searching for alternative solutions to sucky fonts in Chrome/Chromium, I ran across this little gem by Aatish Neupane on his blog, Linux Tutorials and Reviews. Now my fonts are pretty again.
I don’t know if Chromium will be my long term browser solution, but for the moment it’s my default browser on all my systems. We’ll see how things go from here.
Further reading: The Chromium Projects
I’ve been married to Mozilla Firefox (and Thunderbird) since I came to GNU/Linux full-time nearly 8 years ago.
I’ve tried other browsers: Epiphany, Midori, IceSkunk — er… I mean Weasel (in Debian), Konqueror (an old fav), etc. I never could get them to do the things that I wanted my browser to do. I used to heavily customize my FF, even using userChrome scripts to manipulate things under the hood. However, lately I’ve gotten FF pretty much just the way I want it. It’s not too bloated. It’s not to graphics intensive to display. It’s just right, in other words.
Unfortunately, sometime in the past few months, FF has developed some CPU cycle hogging tendencies that really are beginning to aggravate me. It usually happens when I first open the browser. Now I clear-all when closing my browser, so I’m starting it back up with minimal overhead. Still, for the first few minutes of operation each day, it gobbles CPU cycles to the point where it actually freezes up while trying to load two or three websites in tabs.
I’ve done all the usual: make sure extensions/plugins are all up-to-date, start in Safe Mode, start with a fresh profile, etc. FF still displays this annoying habit of jamming up CPU cycles when you first start it up. Oh, well… I almost suspect Adobe Flash, but can’t blame everything on them. 😉 When this happened to me first thing this morning, it got me motivated to maybe find a browser alternative to FF for a while.
I already had Opera installed on my Slackware, so I updated it. I then installed Chromium (not Chrome, but close enough) from a SlackBuild from Alien Bob’s (Eric Hameleers) repository. You’ll be getting a substantial donation, Eric, if I can ever get my personal finances in order again. Anyway, I played around with both Opera and Chromium for a while. I’m just daunted by the amount of work involved to get them to do what my FF already does so well. It’s going to be tough to break away from FF, I thought…
Well, Fran (Li’l Bambi @ Scot’s Newsletter Forums) mentioned an alternative that I had heard of, but had forgotten all about up until I saw her posting today. She mentioned The Pale Moon Project. I immediately went over to their site to have a looksee. I was impressed with what I saw there. What really had me jumping for joy was the fact that Pale Moon would work with existing FF profiles. That would save me a lot of work when it comes to setting up. So, I figured I’d give it a try.
A screenie thumbnail of my Pale Moon browser
Since I’ve run Slackware as my primary operating system on all my machines for almost 8 years now, I knew that I’d probably have to compile this on my own from source code that I downloaded from the Pale Moon folks. Well, surprise! Their little tar.bz2 package actually has a minimal install script included. It worked like a champ in Slackware. No muss, no fuss. I had the browser installed in less than a minute. All I had to do after that was copy my default FF profile into the Pale Moon directory and change the profile.ini to point to it.
Whammo! I’m using Pale Moon right away. It opens the very first time looking and functioning 99.9% like my FF; Bookmarks, extensions, addons, plugins all working right off. Impressive! I’ve been using this browser all afternoon today. It hasn’t burped once. The only time I see any significant CPU usage is when scrolling on highly graphic intensive pages, like Bing Image Search or similar, but nowhere near the CPU usage that FF was displaying. It also seems to be a bit faster to respond, but that could just be my imagination.
Of course, I haven’t tested thoroughly, but after the few hours that I have been using Pale Moon, I’d have to say it’s a solid little app. I would definitely recommend it to folks who love their FF, but want something just a wee bit lighter. Pale Moon is based on FF 24.5 ESR, which is perfect for me because that’s exactly the version that Slackware 14.1 is using right now; 100% profile compatibility.
I like it. You might, too. Give it a shot. And if it turns out you do like it, click that little donation button on the Pale Moon website. $5 or so wont put you in the poor house. 🙂