Firefox 36.0.1 fixes a number of critical issues - gHacks Tech News

Firefox 36.0.1 fixes a number of critical issues

Mozilla has just released Firefox 36.0.1 to which fixes nine issues in the browser. The new version is already distributed via the browser's automatic updating system and also available on the official website from where it can be downloaded to upgrade Firefox manually instead.

To make sure Firefox picks up the update right away, tap on the Alt-key and select Help > About Firefox from the menu.

This initiates a check for updates which should pick up the new version right away. To test which version of the browser you are running, type about:support and look there under application basics.

The new version of Firefox fixes several issues among them a top crash and a startup crash on systems with Microsoft's Enhanced Mitigation Experience Toolkit running.

firefox 36.0.1

The new version on top of that fixes the following issues / restores the following functionality in Firefox Stable:

  • The -remote option that Mozilla removed in Firefox 36 is available again. The reason for bringing it back appears to be that the removal affected more users and software products than Mozilla thought it would. According to the Bugzilla listing, it affected Python, Emacs, any add-on or software working with multi-profiles, and also Eclipse.
  • The use of ANY DNS has been disabled. It disables the use of ANY DNS to get the TTL on Windows. There is a lengthy discussion about this on Bugzilla but it appears that DNS ANY was used in contexts where it should not be used.
  • Fix of a massive memory leak. More information about that here.
  • Fixed a issue where print preferences would not be saved from print job to print job. Firefox 36 reset print preferences for jobs and this bug fixes the issue. More information here.
  • Fixed hostname with underscore rejections in Firefox. Firefox displayed an untrusted connection warning if a subdomain used an underscore in its name. Bugzilla has more information about the bug.
  • Two Hello issues were fixed. The first resolves an issue where contacts were not loaded when you sign in with a Firefox Account (Bug 1137141), the second that Hello might become inactive after a restart (Bug 1137469)

You find more information about the fixes in the official release notes. The memory leak fix and the two crash related fixes should be reason enough to install the update as soon as possible. Obviously, if you have been affected by the other issues fixed in Firefox 36.0.1 then you may want to install the new version as well right away.

For information about Firefox 36, check out our overview of that here.

Summary
Firefox 36.0.1 fixes a number of critical issues
Article Name
Firefox 36.0.1 fixes a number of critical issues
Description
Firefox 36.0.1 is a stable version update for Firefox that fixes several issues in the browser including crash and memory leak related ones.
Author

We need your help

Advertising revenue is falling fast across the Internet, and independently-run sites like Ghacks are hit hardest by it. The advertising model in its current form is coming to an end, and we have to find other ways to continue operating this site.

We are committed to keeping our content free and independent, which means no paywalls, no sponsored posts, no annoying ad formats or subscription fees.

If you like our content, and would like to help, please consider making a contribution:

Comments

  1. RG said on March 5, 2015 at 9:28 pm
    Reply

    Firefox has memory leak issues? Shocking

    End Sarcasm ;)

    1. Who cares said on March 5, 2015 at 9:55 pm
      Reply

      They get better and better in copying Chrome :D

    2. Pierre said on March 6, 2015 at 3:35 pm
      Reply

      lol

    3. Sugram22 said on March 15, 2015 at 11:11 pm
      Reply

      i still have memory leak, well only when i watch videos & it gets wore when i go full screen, Win 8.1

      post i made to mozilla support, my last post, copy paste:

      i haven’t used full screen a week & that reduces the issue a lot, max memory with day, from 240MB-460MB (max 540 sometimes), with full screen its 240-700, with waterfox 340-1,4GB, with waterfox it started to have small 1sec-2sec crashes at 1,4GB, with firefox it has not reached a crash point yet, but when memory just grows like that with out releasing, with out going pack to 240 after closing video tab then it feels like something is wrong (& after that when i open new video tab or just click next with out closing memory number grows), with 1 video tab – bookmarks opened in tab & 1 simple page opened, 3 tabs total is around 220-260, it grows with next video i chose, i even have looked adds that should help, but looking at peoples comments they do not work, at least not the way they should or like user expects them to work

      New TXT
      water fox was just a example, the point is that all Fox builds have a issue with flash, with youtube i tried HTML5 & with that there are also issues, 1 issue is that video loads only to a certain point & does not finish loading, it random, a bit over half is minimum point, but i watch TV series to & series i watch from other sites, & in there i can’t escape from flash usage even if HTML5 issues get fixed

      that memory number growing is not normal, when it grows it also should go back to the number it was when video tab is closed, & when i chose next it should only go up for a moment & then go back to the number it was, normal is for me is with bookmarks opened in 1 tab second tab simple web page & 3th tab video 200MB-300MB cause that what it is when i have watched the video, one episode

      MY ADDS:
      Ublocker
      Ghostery, Ghost rank disabled
      Enforce Encryption
      More In Content UI +

      1. clas said on March 16, 2015 at 10:57 am
        Reply

        have you tried firemin for the memory problems…works fine for me.

  2. Martin Jarvis said on March 5, 2015 at 10:40 pm
    Reply

    For those who don’t know how to tell what version of Firefox they’re on, here’s a quick Hint… http://dmjcomputerservices.com/blog/2012/10/11/how-do-i-know-which-version-of-firefox-im-using/

    1. XenoSilvano said on March 5, 2015 at 11:38 pm
      Reply

      You can find-out which version of Firefox you are using on the about screen (the same screen that allows you to upgrade the Firefox through the browser).

      As mentioned in the article above: “To make sure Firefox picks up the update right away, tap on the Alt-key and select Help > About Firefox from the menu.” or ☰ > ? > About Firefox

  3. Doc said on March 5, 2015 at 11:00 pm
    Reply

    36.0.1 also fixed a critical bug for me: The NoSquint and SimpleClocks addons were completely unusable: NoSquint would not apply zoom settings automatically on page load, and SimpleClocks would erase/not be able to load its Time Zone settings, pop up an XPath error when it tried to update them from Google, removing any saved clocks (and not show the icon on the toolbar, requiring a removal and reload).
    Glad to see these fixed so quickly.

    1. MJS said on March 6, 2015 at 1:17 am
      Reply

      One main reason I had yet to get the newest version was the NoSquint compatibility issue I had heard about. That add-on is now an essential part of my internet surfing. I’ve become so accustomed to a (easy-on-the-eyes) black background and white text that any of the ‘normal’ loud, bright, white pages is almost painful to stare at. I dream of the day when a black page background will be the standard of the web– Which will probably be the same day that pigs fly, hahah.

      At any rate, over the years I’ve learned to wait a good while on releases, whether it is a browser or most anything else. I keep my system secure at its core, so I’m good on that end. And I have spent WAY WAY more time, energy, and frustration going back to fix or unscrew a buggy ‘update/upgrade’ that I immediately grabbed before they could iron out issues related to reports and feedback. At times, it was as time-consuming or involved as rooting out a freakin malware.

      Thanks Martin for another to-the-point, and easily accessible article put out on the immediate heels of this release.

      1. Doc said on March 7, 2015 at 2:46 pm
        Reply

        Hadn’t heard about the NoSquint compatibility issue when I decided to upgrade; you may also want to try Blacken, which lets you improve contrast on pages with a click or two.

  4. XenoSilvano said on March 5, 2015 at 11:09 pm
    Reply

    That explains why Firefox has been acting-up, it tends to stall quite frequently (even as I am writing this), it sometimes brakes-down completely, Windows has also been showing me notifications about how Firefox is causing the system to run out of memory.

  5. Torro said on March 6, 2015 at 12:08 am
    Reply

    @ Martin

    Unfortunately, the link you posted for manually downloading 36.0.1, does not give the updated version. It just gives version 36.0.

    The stupid updater has not worked for me since 34.0, FF just hangs and never completes installation of updated FF. So I have to update FF manually. Do you have a confirmed 36.0.1 version link somewhere?

    EDIT:

    Did a search and found where to get the 36.0.1 version located here

    https://www.mozilla.org/en-US/firefox/all/

    1. Martin Brinkmann said on March 6, 2015 at 8:05 am
      Reply

      Thanks. Strange that the main link was not updated by Mozilla yet (for all languages). I just tested again and it should be live now there.

  6. Torro said on March 6, 2015 at 12:28 am
    Reply

    The download link you gave, only gives 36.0 and not the updated 36.0.1 version.

    I had to get the 36.0.1 version here

    https://www.mozilla.org/en-US/firefox/all/

  7. imu said on March 6, 2015 at 12:53 am
    Reply

    Hi Martin,I think you should take a look at this http://www.dedoimedo.com/donate.html. just came across and thought this might be something you are not aware of.

    1. Martin Brinkmann said on March 6, 2015 at 8:03 am
      Reply

      Interesting. I’m currently looking at other options. I plan to set up a Bitcoin account this weekend for instance.

  8. Boris said on March 6, 2015 at 1:25 am
    Reply

    I hope Cyberfox will fix this stuff as well. The same memory leaks.

  9. Dwight Stegall said on March 6, 2015 at 3:00 am
    Reply

    You can bookmark the updater page chrome://browser/content/aboutDialog.xul

    1. Boris said on March 6, 2015 at 5:48 pm
      Reply

      Never mind, Firefox did not fix anything. After mild usage for 1 hour memory is up 400Mb and is not going back down. It looks like I am staying with Cyberfox for a heavy usage since it can take more memory that delays crashes and slowdowns by few hours.

      1. clas said on March 7, 2015 at 10:35 pm
        Reply

        try firemin

  10. Italian Plumber said on March 6, 2015 at 2:36 pm
    Reply

    What about this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1067470? It’s one of the most annoying bugs I’ve ever experienced in Firefox.

    1. Boris said on March 6, 2015 at 5:44 pm
      Reply

      This is very annoying bug. It usually happens after an hour of Firefox uptime and on some specific websites like IMDB. For heavy users this bug is a killer. Try opening 20-30 webpages in few seconds and then flip through them. This bug will drive you mad.

  11. Terence said on March 6, 2015 at 6:30 pm
    Reply

    This useless update took effect this morning and now my online banking website is no longer fully encrypted, with no SSL server certificate and an orange and black triangle instead of the padlock :
    https://my.if.com/Security/Auth/Logon
    It’s still fully encrypted using I.E. so it’s not the bank’s website at fault and was fully encrypted with Firefox yesterday with version 36.0. Since my bank has very few customers I doubt the’ll bother fixing it. Is there any way I can revert to the previous version of Firefox?

    1. dszady said on March 7, 2015 at 3:32 am
      Reply
    2. Ronald said on March 7, 2015 at 8:17 am
      Reply

      You should file a bug anyway, can’t hurt.

    3. Terence said on March 13, 2015 at 5:07 pm
      Reply

      It seems I was wrong to blame Firefox as the Intelligent Finance website is at fault. Their SSL Certificate is signed using the obsolete sha1 with RSA Encryption, the weak RC4 cipher and the server where their website is hosted only supports older protocols, not the current best TLS 1.2.

      The server needs reconfiguration. The latest version of Firefox has merely been updated to recognise the weak cipher, hence no green padlock. From what I understand Firefox 38 onwards will stop supporting RC4 ciphers and completely block access to affected sites, as will rival browsers eventually. Naturally I have raised the issue with Intelligent Finance who who seem to be taking the matter seriously and say their IT people are invsetigating.

      1. Charles said on April 20, 2015 at 12:48 am
        Reply

        Thanks – I’ve just hit the same problem, good to know they’re trying to fix it, but a tad worrying that an internet banking site doesn’t update their security more often…

      2. Terence said on April 20, 2015 at 6:56 pm
        Reply

        Charles, if you’ve upgraded to FF37.01 by now you’ve probably found, like I did, that Firefox now blocks the bank’s login page entirely, having now ceased to support RC4 ciphers. The best fix is to tweak the ‘about:config’ page to make a site specific exception for your bank. Double-click the security.tls.insecure_fallback_hosts preference. Then, in the box that comes up, paste the host name of your bank. Click OK , save and access should be restored as before – with the insecure orange triangle of course.

      3. Charles said on April 22, 2015 at 12:30 am
        Reply

        Super helpful – thank you!

      4. Huw said on May 21, 2015 at 11:33 pm
        Reply

        While we wait for if.com to pull their finger out and improve their TLS implementation, there is a workaround in firefox to permit the out of date security.
        Open a new tab and enter “about:config” to access the more complicated settings. Search for “tls” and you should see the security.tls.version.fallback-limit setting which now has the value 3 by default (which means TLS 1.2). Set this value to 1 to permit TLS v1.0 which if.com still uses.
        See http://kb.mozillazine.org/Security.tls.version.* for more details.

  12. MichaelK said on March 9, 2015 at 11:16 am
    Reply

    There is still an issue with access to network devices on my intranet with self signed certificates. When I clink on the “add exception” button on the warning page nothing happens and I can not add the exception manually either under the “Tools –> Options –> Advanced –> View Certificates –> Servers” menu :(

    I have been using Firefox since it was named Netscape, but have now been forced to move to Chrome :(

    Buh Bye Mozilla, it was fun while it lasted.

    1. Firefox User said on March 9, 2015 at 3:05 pm
      Reply

      I am seeing this issue too, starting with 36.0.1. It is very annoying, and is forcing me to use another browser for self-signed certificates.

  13. kath g said on March 13, 2015 at 12:31 am
    Reply

    This is the worst firefox version I’ve ever had….it hangs a lot, unresponsive scripts all over, and any flash content on a page makes a page take forever to load. I’m not a computer guru and have spent many hours trying to rectify these problems from read articles, tech articles, uninstalling and reinstalling things, etc. with nothing working.

    One of the reasons I have used firefox for MANY years is that it is user friendly…this version is not for me….enough so that I may have to switch browsers. I don’t understand code and don’t want to mess with it. Usually when ff had a problem it wasn’t this serious and the next version fixed it, so far this has not been the case.

    If I can figure out how to go back to a working ff without losing my bookmarks, etc. I’ll try that before abandoning it altogether. I’m really disappointed in ff 36.0.1.

  14. Cat said on March 14, 2015 at 12:19 am
    Reply

    This thing goes unresponsive literally every time I start it up, even if I haven’t even opened a bloody tab yet. I disabled all my add-ons, turned my computer off and on again and checked my CPU’s activity to see if anything weird was going on but no, it’s just a BAD UPDATE. I feel like I’m using Chrome on Windows 95.

  15. bakatas said on March 17, 2015 at 3:25 pm
    Reply

    The problem with unresponsive button are fix when you go to older version of firefox.

Leave a Reply

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

Please note that your comment may not appear immediately after you post it.