Farewell, Firefox

In the eyes of many of my associates, I am probably a bit late coming to this realization: Firefox has memory issues that are just not going away. I've tried to work around this by using another browser for any "important" browsing. I've tried re-installing different versions of Firefox. I've just tried exporting my bookmarks and uninstalling it permanently, and that seems to have fixed the issue.

For reasons that I cannot fully explain, I've been finding myself more and more making excuses for my continued use of Firefox. I used Chrome to launch links, and run "web apps" like the Google suite, but I was doing my "surfing" on Firefox. It has a fuller interface. It had a deeper library of add-ons. Prettier themes. Whatever.

One reason I've hung on to Firefox was because it was a slick open source application and, as such, it deserved my support. Sure, Chrome was a fast loading alternative with a growing library of add-ons, but it was owned by The Man, not The People. Surely I owed Mozilla another chance to stabilize. But I've since come to admit that I don't. Mozilla/Firefox was giving me the same low-grade service level that caused me to fire my last ISP.

Every few months, I get an email from an update to a bug concerning memory leaks I submitted to Bugzilla a while back. It's usually someone else saying something like, "Hey, guys? Still broke."

I submitted the bug for version 0.4.

So, this morning, when Firefox froze up on me in the middle of filling out a long form, I waited to see if it would clear up. It didn't. I popped up Task Manager to see what the process was doing. It was busy eating up a quarter of my memory and growing. I killed it and loaded it again. It never finished reloading the four tabs I'd had open. I killed it again.

Then, mentally tabulating the hours I've spent waiting for Firefox to get unhung, I went ahead and removed it. It was a little sad.

I'll miss you, Firefox. You used to be so cool.