I love using Firefox as my primary browser. I prefer using it for a variety of reasons. Lately, though, I've noticed that it's become a bit of a resource hog, and I can't work out why?
I love using Firefox as my primary browser. I prefer using it for a variety of reasons. Lately, though, I’ve noticed that it’s become a bit of a resource hog, and I can’t work out why? I’ve disabled add-ons that I don’t need, and it still uses about 1.4GB of RAM at a minimum for pages that Chrome uses a quarter of RAM for.
Has something changed in Firefox’s architecture? One thought I had is that maybe this has to do with something like page pre-fetching (I think Firefox does that), or something along those lines. I want to sort this out. Chrome seems to be so much better at resource management at the moment.
Firefox 55 was released on the stable channel yesterday and it is also pretty snappy. Chrome is starting to feel a little sluggish by comparison (although it’s possible that I’m imagining it).
I found myself thinking back to the marketing campaign for Firefox 3 back in 2008 (I think). At the time, Firefox wasn’t on its current 6-8 week release cycle so developments took a bit longer.
For some reason, Firefox 3 was a big deal back then. I don’t remember why but I do have a vivid memory of the robot imagery that Mozilla used to publicise the release. I found this image on Flickr earlier this afternoon.
Almost a decade later, there is still something about this robot imagery that I love.
Firefox making moves on Chrome
If you’re curious about this “new” Firefox that people are talking about lately, you may find this article interesting:
It’s tempting to just dismiss this browser as a “has been” and stick with Chrome. Chrome is a great browser and dominates the Web. Still, I think having a spunky challenger with a strong focus on an inclusive and open Web is important.
Just as it successfully challenged Internet Explorer back in the day, Firefox could help keep Chrome in check where it counts.
I’ve been a Firefox fan since Firefox was in pre-1.0 beta. Even though it isn’t my primary browser at the moment (wait 5 minutes, my defaults can change without notice), I still love what it stands for and the work the Mozilla Foundation is doing. This video nicely encapsulates that mission:
I love this idea that the web was built by hand (which, if you think about it, it was). Firefox may not be the hot browser right now but it is largely the reason why we have a more open web today.
Clicking a button within a webpage puts a blinking text cursor in the body of the site, as if editing a Word document. It’s not causing any other problems besides being really annoying and distracting, but it only just started today. I’ve tried restarting Firefox with add-ons disabled, as well as reinstalling Firefox clean.
Fortunately the solution turns out to be pretty simple:
This is likely caused by switching on caret browsing and you can toggle caret browsing on/off by pressing F7 (Mac: fn + F7).
There are other ways in which Mozilla’s DRM is better for user freedom than its commercial competitors’. While the commercial browsers’ DRM assigns unique identifiers to users that can be used to spy on viewing habits across multiple video providers and sessions, the Mozilla DRM uses different identifiers for different services. And unlike the commercial browsers’ DRM, the Mozilla implementation does not intentionally leak any information about the user’s system or its configuration to video services.
I noticed some off rendering issues in Facebook when I view this site in Firefox (pretty much the last few versions), compared to Chrome. This is what this site looks like in Chrome:
This is what the site looks like in Firefox (I’m running the stable version 11):
I notice 2 issues in Firefox’s rendering. The first is that the grey background visible in Chrome gives way to a black background in Firefox. The second is the horizontal scrollbar at the bottom of Firefox suggesting there is more on the page to the right of the visible area (there isn’t).
I contacted Squarespace Support about this a while ago when I was running a beta version of Firefox and received the usual response that they don’t support beta browser versions but this issue has persisted. I’m going to point them to this post when I submit a ticket but I’m curious if anyone else has any ideas about possible causes.