Firefox 15 Released: Silent Updates, Compressed Textures, Add-on Memory Leak Fix
Mozilla released Firefox 15 today, and it brings a number of interesting changes. First, the browser is finally switching to a "silent" update model, like Chrome. (No doubt in answer to endless complaints about their rapid release cycle.) In addition, Mozilla says they have "now plugged the main cause of memory leaks in Firefox add-ons." Add-ons commonly hold extra copies of sites in memory when they don't need to, and the browser now has a mechanism to detect this and reclaim the memory. Another significant improvement is the addition of native support for compressed textures in WebGL, which is a boost for high-res 3D gaming. Here are release notes for the desktop and mobile versions.
Last thing I need is for an idiot in some far and distant place to think it fun to roll out a new version and trigger an update on all my computers that may render all the corporate apps unusable. No, thank you. FF joins Chrome in the sandboxed "use only if indispensable" bin.
Every time Firefox upgrades, it wipes out my login cookies. It forces me to re-login to my sites. Is there a way to turn this dictator off?
Never trust a man wearing a coat and tie!
Look, I mean you probably found a bug. The thing to do is to either post on the project mailing list or file a bug report.
Posting a comment on Slashdot is unlikely to result in a solution.
There's no -1 for "I don't get it."
the browser is finally switching to a "silent" update model, like Chrome. (No doubt in answer to endless complaints about their rapid release cycle.
So people have been complaining about Firefox's Rapid Release Cycle -- more correctly called Rapid Version Number Inflation -- and so Firefox's solution is to continue doing it and just not tell you about it.
Brilliant.
Mozilla says they have "now plugged the main cause of memory leaks in Firefox add-ons."
Er, the same memory leaks they assured us weren't happening or weren't their fault?
I have to give them credit. The Firefox devs have quite a sense of humor.
I remember when they claimed that Firefox's excessive memory usage was a feature not a bug -- i.e., Firefox was caching pages. Which is really great except that it wasn't true.
Did they fix Flash freezing all the time, or is that Adobe's fault?
Adobe fixed it by end-of-lifing Flash. Thanks Adobe.
When all you have is a hammer, every problem starts to look like a thumb.
Oh hey, look, it works for everyone else, guess we can ignore you then!
No codec rules the market forever. You might as well have been saying "dude, mp2 rules both audio and video, give it up" fifteen years ago, or "dude, audio is MP3 and video is DIVX and that is that" nine years ago.
The MPEG cartel doesn't believe you either; they've been rushing to get new codecs together (USAC/Extended HE-AAC, H.265).
This time they were beat to the punch. Opus significantly outperforms MP3 and AAC even at their strong points, and MP3 and AAC are very poor for low-bandwidth use and zero use for low-latency communications. USAC is late to the party, high-latency, and doesn't match Opus's quality.
Opus may not totally displace MP3 and AAC for music player use, but it will gain a place there, just as AAC did, and in many of the markets it competes in- especially low-latency Internet audio- there is no well-established competitor.
At the risk of killing my Slashdot cred: I love Firefox.
I have not noticed any memory leak problems, my 15+ Add-Ons have not broken with FF updates, I do not care what version they call it (major or minor number updates) and I can not remember when it last crashed on me.