Shame it doesn't automatically upgrade you from 32 to 64 bit.
Mozilla looses Firefox 43, including Windows 64-bit variant
Mozilla has released version 43 of its Firefox web browser, introducing a 64-bit version for Windows and crushing four critical and seven serious vulnerabilities. The browser should now enjoy the security and performance boosts of 64-bit systems with fatter heap sizes to help fire up things like browser games and better …
COMMENTS
-
-
-
-
Wednesday 16th December 2015 19:26 GMT DrXym
Re: Firefox 43! Now Using Three Times More RAM!
"Firefox 43! Now Using Three Times More RAM!"
More realistically probably 1.2-1.5 times as much. Depends how they hold refs to Javascript in memory. Running a 32-bit app on a 64-bit OS isn't free either and goes through thunks and shims so it's not all one way. In addition 64-bit programs have access to more registers so they might perform faster despite their higher memory overheads. It's probably worth going 64-bit if you have 8GB or more.
People make a big deal of memory consumption but modern browsers including Firefox take the reasonable stance that if you have free memory that they may as well use it to improve performance.
-
-
-
-
-
-
-
Wednesday 16th December 2015 14:56 GMT Dave K
Re: Add-on compatibility
Or you run into other issues, such as with FlashBlock where the current download points you to a version released in November, because the later version released in early December to fix some issues has yet to be signed.
Thankfully, Pale Moon doesn't enforce the silly signing thing, so the later version works without hiccups. Interestingly, I find it strange that Mozilla are only just releasing 64bit Firefox into the wild, whereas Pale Moon, Waterfox and other such forks of Firefox have been happily available in 64bit mainstream versions for years....
-
-
-
-
Wednesday 16th December 2015 20:56 GMT DrXym
Re: woohoo!
Firefox (and other modern browsers) allocate memory if you have a lot free in order to cache content, hang onto compiled JS and so on. Once system memory starts getting short (e.g. because you start a game or another large app), browsers respond by releasing some of that memory.
Would you rather the memory just sat there unused?
-
-
-
Wednesday 16th December 2015 11:14 GMT Dan 55
Re: First impression
Try setting xpinstall.signatures.required to false in about:config, maybe you'll have to close and open the browser afterwards.
This is planned to stop working in Firefox 44 so you'll need to change over to the ESR build before the next update if you still want unsigned addons to work after then.
-
Wednesday 16th December 2015 14:54 GMT Werner McGoole
Re: First impression
Yep, this version of Firefox now enforces signing of extensions, although there is still an over-ride switch - at least until the next version, when that disappears. The need to have every darned extension signed by Mozilla has been heavily criticised by those who develop extensions for their own use, both on ease-of-use grounds plus the fact it can't possibly work. But Moz has pushed on regardless.
Except that there has been a recent change of heart as the reality of what they are doing has become clearer (https://blog.mozilla.org/addons/2015/12/01/de-coupling-reviews-from-signing-unlisted-add-ons/). From the way the announcement is phrased, you could easily miss what it means. In rough translation, it says:
"If an extension isn't going to appear on the official Mozilla site, then they will automatically sign it (via a web API) with no checks whatsoever."
Yes, it would appear that Mozilla are so determined that signing is a "good idea" that they're now prepared to sign code from anyone, anywhere; malware or not.
-
-
-
Wednesday 16th December 2015 10:03 GMT pip25
Article missed the most important change
Signing addons is now compulsory, non-signed addons are disabled upon upgrade, which causes the issues other commenters experienced. You can override this with an "about:config" flag, but they want to remove that flag in the next release, making addons no longer supported by their developers completely unusable. Let's just say I'm less than thrilled about this. :/
-
Wednesday 16th December 2015 10:25 GMT tiggity
Re: Article missed the most important change
Mozilla seem determined to trash what users liked about Firefox, e.g the recent chrome aping (lack of) menus irritated many users.
Now as the huge ecosystem of addins / extensions is the only real advantage of Firefox, they seem determined in breaking that too
-
-
Wednesday 16th December 2015 10:31 GMT The Travelling Dangleberries
Old style search engine picker only available with CTR
The new style search box is now "compulsory" as the about:config fix has gone. You need Classic Theme Restorer to get the old drop down search engine picker back.
I usually have six DDG and six Google search engines for searches in different countries/languages installed in my browsers. The new search engine picker just presents me with six identical icons and I need to hover over each to see which one it which. The old search box drop down allows me to see the titles of each search engine which makes locating the right one very easy.
Yet another unhelpful UI change from Mozilla for no obvious benefit.
-
Thursday 17th December 2015 10:10 GMT Saul Dobney
Re: Old style search engine picker only available with CTR
I do a load of research and f you do regularly swap between search engines for different searches (eg Google in various countries, dictionaries, manuals, encyclopedia, film sites, Amazon, scholar cross-checking) the enforced switch to the new style search is really frustrating. The new style is just so clunky, unintuitive and such a step backwards.
Things like if you've entered some text, choosing a search engine runs the search instead of switching the suggestions list. And there is initially no obvious indicator of which search engine is default on the menu line - so if you have to start typing to know which search engine is set. At least in the old release you could turn the new style off.
-
Wednesday 16th December 2015 12:33 GMT Richard Lloyd
Had 64-bit Firefox for ages...
Linux has had official 64-bit Firefox for ages and even Windows users have had both official (nightly) and unofficial (Palemoon/Waterfox) 64-bit builds too, so 64-bit isn't big news for those who really wanted it on Windows.
One minor relief on the Linux side is that they've postponed the move from GTK+2 to GTK+3 until maybe version 45 in March next year - at which point it would break on at least one prominent LTS distro (CentOS 6) that's got support until Nov 2020.
-
-
Wednesday 16th December 2015 16:53 GMT Greg J Preece
Re: How about "World has flushed Firefox"?
Modernisation like getting a 64-bit version out (about time too)?
Security updates like the ones described in the article?
Getting plugins signed to help fight against, amongst other things, malware?
Do you people even read the articles any more, or do you just see a piece of software you don't use and immediately start writing the comment slagging it off?
-