Mozilla Firefox 10.0.1 Update About To Be Released

Martin Brinkmann
Feb 10, 2012
Updated • Feb 10, 2012

Mozilla, developers of the popular Firefox web browser, have just released an update for the browser's stable branch that moves the version to 10.0.1. The release may come as a surprise to users of Firefox 10, who were updated to that version only ten days ago.

This is not the first occurrence that a critical update is released shortly after a major version upgrade of the web browser. Similar updates had to be delivered after the release of Firefox 9 and Firefox 8.

Firefox 10.0.1 fixes critical issues that came to light shortly after Firefox 10 had been released to the public. This includes at least one startup crash when the browser is opened by the user, and one Java related issue that is causing text fields to hang in the browser. Firefox users can resolve that issue manually by minimizing or resizing the browser. The patch released later today will fix the issues permanently though.

The product planning summary lists additional issues that the developers are currently looking into. This includes issues with AVG's SafeSearch extension that is blocking the enter key from functioning correctly in the browser's address bar. While it it possible to click on the go button to be taken to the site, it is a issue that the developers want to resolve as quickly as possible.

Other issues mentioned in the summary are additional crashes, and incompatibilities with Norton products and RealPlayer Video Downloader.

The release is already available on the Mozilla release ftp server and on third party download portals such as Softpedia. It is likely that the new version will be pushed to all users later today. At that point it will also be offered for download on the Mozilla website and as an update in the browser.

Please note that both the standard Firefox 10 build and Firefox 10 ESR will receive the update to Firefox 10.0.1.


Tutorials & Tips

Previous Post: «
Next Post: «


  1. Someguy said on February 11, 2012 at 3:46 am

    Have they fixed the massive memory leaks yet? I can leave a single-tab FF session open just on Google and overnight it’ll gobble half a gig of RAM for no reason.

    Chrome might be better, but it’s more memory for every tab you open. It’s kind of sad when the oft-maligned IE has better memory management than alternatives that build up their brands on the user base slamming IE.

    1. Hy said on February 11, 2012 at 8:43 am

      I agree, I am sorry to say. I ran FF8, 9, and 10 the last few months, and with multiple tabs (30, 40, 50, etc.) open for only a few hours memory usage was up to a gig or almost a gig and a half, and browsing became noticeably slower. Only closing and reopening FF would help. This was with Bar Tab-like addons, not loading tabs on startup, etc., and on an otherwise very fast, new, loaded machine. Although I liked newer features like app tabs and especially tab groups, I had to go back to FF3.6 recently, because it performs so much better with many tabs open. How sad that Firefox’s memory problem is getting significantly worse. And what I really wonder is: can this memory problem EVER be fixed? If so, why haven’t they fixed it already?

  2. Paul(us) said on February 11, 2012 at 3:31 am

    Will, It happened by my to, I thin probably because Firefox could not handle a add-on update and a version upgrade at the same time. When I restarted main Firefox version update there where no troubles at all.
    Ans sorry Martin i forgot the mention by name with the fileforum release update.

  3. Will said on February 11, 2012 at 2:16 am

    I accepted the 10.0.1 update and when it was applied … it crashed.

    Not a good start.

  4. Anonymous said on February 11, 2012 at 12:30 am

    I found the already (at the same time main browser update automatically) the update on:

  5. Redbad said on February 10, 2012 at 8:10 pm

    Congratulations to Bob in Accounting who wins $75.00 in the “Firefox dot one version When?” office pool for nailing it with his prediction within 30 minutes of the announced release! Stay tuned for the next pool for 11.0 and 11.0.1.

  6. OSS said on February 10, 2012 at 5:33 pm

    Well, much as some of us may hate the quick release cycle, it’s perhaps time to get used to it. Personally, the release cycle is too fast yes. But till now, it has not changed/screwed up any of my firefox settings (touchwood!:). So, I’m not complaining.

    This appears to be a stability update (problems with third party plugins (Norton products and RealPlayer Video Downloader).

    “Rant begins”

    For people who think their addons break with each version, use the addon compatibility reporter.

    For people who think that the 3.6 series rocks, you still have the latest 3.6.26.

    For people who think the updates are useless, disable them. Problem solved:).

    Yes, it does become very, very tiresome to:

    1. Allow Firefox to download the update.
    2. do a restart.
    3. Get back to browsing.

    I mean that is such a difficult thing, is it not? Takes a couple of minutes, I’m guessing. Jokes apart, the updates (though they are frequent) are a good thing.

    “Rant ends”

  7. Roy said on February 10, 2012 at 3:33 pm

    Three times running – more proof that the 6 week rapid (let’s just copy Chrome) release cycle is flawed in Mozilla’s case.

    They clearly don’t have time to test properly AND develop worthwhile changes within 6 weeks so should consider moving to a 3 month cycle instead. I doubt they will listen though – Mozilla seem to have lost focus on users which may be why their market share has stopped in its tracks.

    1. aardmaat said on February 10, 2012 at 10:37 pm

      nonsense, other browsers do the same (release quick patches). only difference is that Mozilla is open about it and microsoft, apple and google aren’t

    2. iusafdifya said on February 10, 2012 at 5:09 pm

      Features are developed for six weeks, then tested for twelve weeks. Stop spreading lies.

      1. Roy said on February 10, 2012 at 7:58 pm

        Never said they weren’t – think before insulting. You ignore that it’s a rolling release cycle, in parallel not in series.

        12 weeks testing one version runs alongside new development x 2 and testing of the subsequent version – spreading resources much thinner than if they changed to a 3 month cycle. Project management 101.

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.