Recommended Posts

As a longtime user of Firefox, I couldn't pass up the opportunity to use a 64-bit version of it. I figured I'd give it a try and it's something I've been thinking of doing since I first used Windows Vista Ultimate x64. I honestly never heard of Waterfox until I read this article on Neowin. I installed it on my main PC (Windows 7 Ultimate x64) and I really like it. It definitely feels speedier than the standard 32-bit version of Firefox and things like Flash also feel faster. Another positive thing is that YouTube videos no longer crash my display driver. I assume that using a 64-bit version of Flash had something to do with it.

Anyway, if you have a 64-bit operating system and are open to the idea of using a 64-bit browser than Waterfox is for you. You can download it here alongside its prerequisites.

FAQ:

What is Waterfox?

Waterfox is a high performance browser based on the Mozilla Firefox source code. Made specifically for 64-Bit systems, Waterfox has one thing in mind: speed.

Why should I use a 64-Bit version of Firefox?

For some people with older systems, the 64-Bit version loads quicker and is much more responsive than the 32-Bit build. For people with newer systems, it allows them to use the full potential of their systems.

If there are any bugs, where should I report them?

Unfortunately, since this is a 3rd party build you cannot report any bugs and you?ll just have to hope that they get fixed in the next update by Mozilla.

Is my experience limited if I use a 64-Bit version of Firefox?

The major plugins such as Adobe Flash, Sun Java, Microsoft Silverlight all have supported 64-Bit binaries available.

How does it compare to 32-Bit Firefox?

In benchmarks, the 64-Bit variant of Firefox out-performs the 32-Bit variant. Also because this variant is being built specifically for Windows, there might be further performance increases.

Were there any optimisations made?

Yes, Waterfox was compiled with SSE, SSE2, x64 favoring and the following optimisation flags: /Og /Oi /Ot /Oy /Ob2 /Gs /GF /Gy

Do all my Add-Ons work?

Yes! Add-Ons work on any version of Firefox, on any platform.

I get a msvcr100.dll is missing error.

You must have the Visual C++ Redistributable file linked in the download page installed.

How do I fix the blurry font?

Type about:config in the address bar. In the filter at the top type gfx.direct2d.disabled. Change it from false to true.

http://waterfoxproj....ceforge.net/faq

29l1hn6.png

Link to comment
https://www.neowin.net/forum/topic/1050079-waterfox-64-bit-version-of-firefox/
Share on other sites

I've always wondered just how they produce these 64bit builds, since for a long time the main codebase wasn't 64bit safe. Currently 64bit builds are still slower at JS than 32bit builds, and no amount of compiler optimisations will fix that.

Mozilla still don't consider the 64bit builds ready for anything but developer usage, they still crash randomly and often crash in such a way that the OS never calls their crash handling code (So the bugs go unreported)

I've always wondered just how they produce these 64bit builds, since for a long time the main codebase wasn't 64bit safe. Currently 64bit builds are still slower at JS than 32bit builds, and no amount of compiler optimisations will fix that.

Mozilla still don't consider the 64bit builds ready for anything but developer usage, they still crash randomly and often crash in such a way that the OS never calls their crash handling code (So the bugs go unreported)

I guess that was the case in the past. I haven't tried the 64-bit Nightly builds so I don't know how stable they are over the 32-bit Nightly builds. So far though, Waterfox hasn't crashed once. Perhaps Mozilla finally got around to making Firefox 64-bit friendly. Here's an interesting article about Firefox 8 (64-bit): http://www.extremetech.com/computing/90546-firefox-8-x64-has-64-bit-browsing-finally-come-of-age

I've always wondered just how they produce these 64bit builds, since for a long time the main codebase wasn't 64bit safe. Currently 64bit builds are still slower at JS than 32bit builds, and no amount of compiler optimisations will fix that.

Mozilla still don't consider the 64bit builds ready for anything but developer usage, they still crash randomly and often crash in such a way that the OS never calls their crash handling code (So the bugs go unreported)

I still think Mozilla needs to kill the current code and start from scratch.

Agreed, especially with Google having such a nice clean product as Chrome.

Considering it's withstood the competition quite well, I'm guessing a lot of people would disagree with you.

I'd prefer it if Firefox was optimized for SSE2 like Chrome is, but it's not really a concern if the performance is there. (The 64 bit version will be, of course, since all x64 procs have SSE2.)

Quite a lot of snakeoil and even a surprisingly outright lie, in fact. It is designed in hardware so that x86 code takes zero performance hit when run on an x64 machine. None, period.

As for optimization, setting compiler flags can do little magic if the code is not applicable for it. I would guess that forcing the matter can even make it slower as the dedicated instructions become efficient only when used properly.

As for compatibility improvements that are at least evident, I've, for one, settled for Nightly (and temporarily the latest Tracemonkey if it decides to crash).

I've had Waterfox, Palemoon and Aya... whatwasit for some time, run lenghty benches, too. Results were inconclusive but not something to make an impression that either was better than the other. It is no question that both Chrome and Oprah is faster in most cases. Even IE9 holds up in certain test cases.

All in all, if it works for you, good. If it doesn't, however, better be sure that those loud promises of these custom compiles being the fastest and whatnot are full of very big holes.

It's disappointing to me that the Firefox devs are still waffling over how to do it properly.

Like, we know what we need to do this, and we are making plans to do it, but we don't actually want to do it.

Heh.

They're working on it (see here). Unfortunately, it isn't a high-priority feature.

I guess that was the case in the past. I haven't tried the 64-bit Nightly builds so I don't know how stable they are over the 32-bit Nightly builds. So far though, Waterfox hasn't crashed once. Perhaps Mozilla finally got around to making Firefox 64-bit friendly. Here's an interesting article about Firefox 8 (64-bit): http://www.extremetech.com/computing/90546-firefox-8-x64-has-64-bit-browsing-finally-come-of-age

Even up to the mid point of 2011 they still had random chunks of code that assumed 32bit OSs (Converting pointers to 32bit integer, etc.). As for the article, that's entirely made up, what I think happened is that somebody noticed Mozilla was running 64bit regression tests, and assumed that meant an official release was coming (Which it isn't for a while until they sort all the problems out)

I still think Mozilla needs to kill the current code and start from scratch.

There's no reason to do that, the incremental upgrades they're doing now are much better (Stopping the project for a year to rewrite vs. rewriting a component incrementally over a couple of releases)

...

I'd prefer it if Firefox was optimized for SSE2 like Chrome is, but it's not really a concern if the performance is there. (The 64 bit version will be, of course, since all x64 procs have SSE2.)

It already is.

Have been using waterfox for the last few weeks so far and absolutely no problems whatsoever (same with firefox), constantly kept open for about 10 hours a day and memory usage always around 450MB (high res image threads, about 1GB then).

It is a wee bit more snappier and smooth than firefox 10 I find.

I guess that was the case in the past. I haven't tried the 64-bit Nightly builds so I don't know how stable they are over the 32-bit Nightly builds. So far though, Waterfox hasn't crashed once. Perhaps Mozilla finally got around to making Firefox 64-bit friendly. Here's an interesting article about Firefox 8 (64-bit): http://www.extremete...lly-come-of-age

Been using x64 nightly for months now and has been as stable as the x32 builds sharing almost all the same bugs. No reason not to use it especially now that flash has an x64 plugin.

Well, you say that, but it doesn't explain the devs discussing it as if it isn't used much over here http://groups.google...=64-bit&lnk=ol

The only discussion I can see is about having less code paths (Firefox includes SSE optimised code paths and normal paths, a native 64bit build doesn't need the normal code paths since it can guarantee the CPU can do SSE). And as a side effect it also means the compiler can include SSE functions anywhere, not just in optimised areas (As is done currently due to how compilers work)

Edit: So the question is "Can we use SSE everywhere?" not "Can we use SSE?"

Been using Waterfox for a while now. Even if it's built by Mozilla, it's NOT Firefox, so it has to be better!! Have NEVER liked Firefox.

Can't say as I've never noticed it being any faster than any other browser. All browsers runs blazingly fast on my sytems and the day that some one says about how slow a browser is on their systems, is the day I should go over and fix their computer!

Palemoon, http://www.palemoon.org/ also has a 64bit version, but I use the 32bit version of that on my 32bit machines.

As far as Chrome, if I were to ever use that again, which isn't happening, it would be SRWare Iron, NOT Google Chrome crap!!

What about the Windows Media Player plug-in?

Unfortunately, 32-bit plugins won't work with Waterfox. It's up to Microsoft to release a 64-bit version of the WMP plugin. So far though, the major plugins work: Flash, Java, and Silverlight.

Unfortunately, 32-bit plugins won't work with Waterfox. It's up to Microsoft to release a 64-bit version of the WMP plugin. So far though, the major plugins work: Flash, Java, and Silverlight.

And even the 32-bit plugin hasn't been updated for years, what's up with that!?

The only discussion I can see is about having less code paths (Firefox includes SSE optimised code paths and normal paths, a native 64bit build doesn't need the normal code paths since it can guarantee the CPU can do SSE). And as a side effect it also means the compiler can include SSE functions anywhere, not just in optimised areas (As is done currently due to how compilers work)

Edit: So the question is "Can we use SSE everywhere?" not "Can we use SSE?"

In 32bit code, since we have to explicitly think and do work about every place where we want to do SSE2, and since it's a performance/size compromise, we end up not doing it in many places.

So yes, I know they use it to some degree, but from what I can tell not much.

Been using Waterfox for a while now. Even if it's built by Mozilla, it's NOT Firefox, so it has to be better!! Have NEVER liked Firefox.

Can't say as I've never noticed it being any faster than any other browser. All browsers runs blazingly fast on my sytems and the day that some one says about how slow a browser is on their systems, is the day I should go over and fix their computer!

Palemoon, http://www.palemoon.org/ also has a 64bit version, but I use the 32bit version of that on my 32bit machines.

As far as Chrome, if I were to ever use that again, which isn't happening, it would be SRWare Iron, NOT Google Chrome crap!!

It's based on the Firefox source code so aside from being 64-bit, it's virtually identical to the official 32-bit version.

And even the 32-bit plugin hasn't been updated for years, what's up with that!?

That's one of the issues of using a 64-bit browser. If you use Firefox with a lot of plugins, then Waterfox may not be good. Fortunately, I only use a handful of plugins and most of them have 64-bit versions.

This topic is now closed to further replies.
  • Posts

    • You've tried DuckDuckGo and Brave Search, now get serious with SearXNG by Paul Hill Over the last decade, it has become quite trendy to dump Google Search in favor of privacy-preserving alternatives such as DuckDuckGo, Startpage, and Brave Search. These search engines have done a very good job at highlighting dodgy practices by Google, such as adjusting search results based on what it thinks you’ll like (filter bubble) and stalking you around the web to advertise to you. While these search engines are good starting points when compared to non-private services like Google, there are still quite a few issues with them. For example, both DuckDuckGo and Brave Search require running non-free JavaScript in your web browser, which is comparable to running proprietary software on your computer, meaning you can be sure about what it’s actually doing in the background. Another issue is that these search engines are hosted on the respective companies’ servers, and you are using a service that you don’t control. Finally, DuckDuckGo, while offering privacy features, relies heavily on Microsoft’s infrastructure for its results and, in the past, has permitted Microsoft tracking scripts. If you are looking for a more private search solution than DuckDuckGo, Brave Search, and Startpage, then I recommend taking a look at SearXNG. It is a privacy-respecting metasearch engine that can be used via different public instances, which is useful for mobile users, or you can install it on your computer or server and run it locally with maximum control. Unlike Google, Bing, or Brave Search, which crawl the web and have their own search indexes, SearXNG is a metasearch engine, meaning it taps other search engines, stripping your identifying data, such as IP address, user agent, and cookies, in the process. Your search query is sent to the other search engines you enable before aggregating the results. SearXNG has deployment flexibility. If you are a casual user or a mobile user and don’t want to run SearXNG locally, you can use a public instance that is hosted by someone else. The main problem with this is that you are putting trust in the maintainer of the instance regarding stuff like logs that they may keep; good hosts should have a privacy policy explaining their policies. If you are trying to use SearXNG, you can also install the software on your device and then head to 127.0.0.1:8080 in your browser and search from there. While you don’t have to worry about a third-party admin like the public instances, search engines could ultimately block your IP address if they frown on you pulling in their search results locally. If you want to run it locally, it’s a good idea to use proxies or VPNs to hide your actual IP. You don’t have to worry about this with a public instance, as search engines never see your IP address. The main privacy benefit of using SearXNG is that it isolates your identity from the underlying engines that it’s capable of searching, such as Google and Bing. These search engines will only see requests coming from a generic server, so they can’t profile you and create a bubble filter that influences what results you see. This also ensures that your search engine doesn’t turn into an echo chamber that prevents you from reading alternative points of view. As a free software project, you are allowed to inspect SearXNG to make sure there are no negative features bundled inside. This sets it apart from the privacy search engines mentioned earlier because you can’t check their source code. As a meta search engine, you are not restricted to getting results from one source. Due to the fact that it scrapes content from other websites, your SearXNG instance will periodically get blocked from different providers, so it’s good to select a range of sources as a backup. While enabling all of the services will give you great results, this can make searching slower. I am personally happy with slower searches for the best results, but you can always check which providers are slowing down your search from the search results page and disable them to speed things up. If you want decent results quickly, enable the main search providers such as Google, Brave, DuckDuckGo, Qwant, Bing, and Yahoo. This way, you get wide coverage without the latency. On the Engines tab in Preferences, do note that there are different tabs, such as General, Images, and Videos, with their own providers that can be toggled and are not covered by "Enable all" while on the General tab, so be sure to dig into each. Just a note, if you want to enable everything, press "Enable all" in one tab, then hit save at the bottom of the page, then do the next tab, and so on. If you press "Enable all", then do that in each tab, and then save, nothing will stick. When I had just some of the search engines enabled, I searched “define nefarious” and results came back with the definition of “define” - obviously that was a sucky result. However, when I had everything enabled, it found dictionary pages for the word “nefarious” and even had an inline definition on the sidebar, which is quite nice too - that was delivered by WolframAlpha for anyone wondering! Probably the worst thing about this meta search engine is that the engines you select are saved with a cookie, so you must enable them on every new device you use SearXNG on, including if you decide to go into incognito mode with your web browser. Honestly, I would say this is the most annoying aspect, and perhaps if your browser lets you choose a separate private browsing search engine, then it would be best to use DuckDuckGo for this portion of your browsing. Another weakness of SearXNG is the random blocking of it by search providers. When you are on the results page, expand the “Response time” box, and it will show things like “Suspended: too many requests” or “access denied”. This is why it is good to enable several providers so that there is always a fallback to get results from. I won’t pretend SearXNG will be for everyone, however, if you enable all of the providers and put up with the slower response time, the results can be really amazing. Even if you don’t want to use it as your daily driver, keeping a bookmark handy that links to it is a good idea if you ever feel like doing a deep dive into a niche topic where other search engines are just failing to bring up any good result, due to the amount of sources it looks on. If you’re interested in radical user control over the software you use, installing SearXNG locally can also be a good idea, but be prepared to be temporarily blocked from sites if you trigger bot sensors without a VPN. Personally, I’ve opted to use a public instance, rather than install it myself. If you want to use it via a public instance, head over to searx.space to find a provider. Let us know in the comments if you have used SearXNG or its predecessor, Searx. What do you think about the quality of the results?
    • Dear Neowin, If it is not too much trouble, can you start using the new-ish designations for Insider Preview? "Experimental" is different than "former Dev" as it can apply to different models, eg 26H1 or 26H2 etc, right? No need to seed confusion IMHO. And, please "finally" update your graphics. OK?
    • Did you see their FAQ, its quite good. Have a look in the Advanced section. https://delta.chat/en/help
    • Just install Linux Mint that is a real blessing and many times cheaper because you can continue using your old Windows computer/laptop with the latest Linux updates.
    • Interesting share -- however it does not make sense: Email messages get stored somewhere, so how is Delta Chat "based on email" and decentralized without actually storing anything? By Web3 standard practices, the various Relays would require dedicated storage to make messages available to the recipients (like a large series of message queue channels, akin to racks of traditional post office boxes)... and Contacts must be two-way confirmed in order for encryption keys to be exchanged (ostensibly every key-pair is uniquely bound between sender and recipient) and the Relays would preserve the public keys in order to facilitate message carriage... or every device stores all sorts of keys and contact info. All of this to say, decentralized messaging is like running Bluesky nodes except instead of discovering/browsing public feeds by various posters (at the given node) these Delta Chats would be relaying encrypted messages (via Relays) that only trusted recipients would have the appropriate decryption key (their own private key) to read it. But this doesn't solve the "it's like email" sales pitch. The only way it's like email is that there's encrypted binary stuff being transported from your app into the federated ether of Delta Chat Relays for others to decrypt (hopefully only the intended recipient)... but outside of this federated relays framework, it is absolutely nothing like email.
  • Recent Achievements

    • Week One Done
      Woland13 earned a badge
      Week One Done
    • One Month Later
      Woland13 earned a badge
      One Month Later
    • One Year In
      bernmeister earned a badge
      One Year In
    • Week One Done
      Scoobystu earned a badge
      Week One Done
    • Week One Done
      tuben earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      503
    2. 2
      +Edouard
      226
    3. 3
      PsYcHoKiLLa
      158
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!