Is there any advantage to using a 64 bit browser vs 32 bit?


Recommended Posts

Well, the main two that comes to mind first is that 64-bit browsers can access more memory (beyond 4GB) and can take advantage of better address space layout randomization (ASLR) to improve security, which is a major plus. Security is first and foremost the most important factor here.

 

The latter one alone is enough reason to use a 64-bit browser over a 32-bit one, in my opinion. The downside to using 64-bit browsers is they will use more system resources (e.g. memory usage will increase), which IMHO is a non-issue with newer PC hardware with adequate amounts of RAM. Also keep in mind macOS is 64-bit only now, along with some GNU/Linux distros considering or already have dropped i686 (32-bit) OSes altogether, like Arch Linux (this doesn't affect multiarch - you can still run 32-bit apps on 64-bit Arch Linux and will continue to do so).

 

It's also a matter of time Microsoft drops 32-bit Windows altogether. You can still run 32-bit applications on 64-bit Windows thanks to the WoW64, and I don't see this going away at all anything soon. It's also a matter of time you will start to see browser vendors phaseout 32-bit versions of browsers, as 64-bit browsers are pushed as the default choices and adoption increases.

Edited by Boo Berry
  • 3 weeks later...

Google has been offering 64bit versions of Chrome since version 37 (the first official 64bit edition of Chrome).

And Mozilla had offered 64bit versions of Firefox for 64bit mac & Linux platforms for a long time but finally offered an official 64bit version for x64 Windows starting with Firefox version 43 in December 2015.

  • 1 month later...
On 3/7/2017 at 7:31 AM, Boo Berry said:

Well, the main two that comes to mind first is that 64-bit browsers can access more memory (beyond 4GB) and can take advantage of better address space layout randomization (ASLR) to improve security, which is a major plus. Security is first and foremost the most important factor here.

 

The latter one alone is enough reason to use a 64-bit browser over a 32-bit one, in my opinion. The downside to using 64-bit browsers is they will use more system resources (e.g. memory usage will increase), which IMHO is a non-issue with newer PC hardware with adequate amounts of RAM. Also keep in mind macOS is 64-bit only now, along with some GNU/Linux distros considering or already have dropped i686 (32-bit) OSes altogether, like Arch Linux (this doesn't affect multiarch - you can still run 32-bit apps on 64-bit Arch Linux and will continue to do so).

 

It's also a matter of time Microsoft drops 32-bit Windows altogether. You can still run 32-bit applications on 64-bit Windows thanks to the WoW64, and I don't see this going away at all anything soon. It's also a matter of time you will start to see browser vendors phaseout 32-bit versions of browsers, as 64-bit browsers are pushed as the default choices and adoption increases.

32 bit Windows is more efficient on RAM and has an advantage on low-spec hardware and also in running a lot of VMs. So not sure they will get rid of it soon.

 

The main practical difference is RAM. The 32 bit browser will only access 2 gig or 4 gig RAM.

 

64 bit browsers are only limited by actual RAM in machine.

 

Makes a HUGE difference in number of TABS and Windows the browser can handle.

 

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Vivaldi version 8.0.4033.50 released June 17: https://vivaldi.com/blog/desktop/minor-update-eight-8-0/
    • The Online part hasn't even been announced and probably won't be included on day one. This is a massive singleplayer game.
    • While I agree with all that, it just proves there's an a** built for every seat.
    • Lol are you mad because I'm not using AI? I'd rather pay people than lose a bunch of potential customers and get humilated because I used AI. A lot of people won't purchase a game if it used AI during development.
    • LibreWolf 152.0-1 by Razvan Serea LibreWolf is an independent “fork” of Firefox, with the primary goals of privacy security and user freedom. It is the community run successor to LibreFox. LibreWolf is designed to increase protection against tracking and fingerprinting techniques, while also including a few security improvements. This is achieved through our privacy and security oriented settings and patches. LibreWolf also aims to remove all the telemetry, data collection and annoyances, as well as disabling anti-freedom features like DRM. LibreWolf features: Latest Firefox — LibreWolf is compiled directly from the latest build of Firefox Stable. You will have the the latest features, and security updates. Independent Build — LibreWolf uses a build independent of Firefox and has its own settings, profile folder and installation path. As a result, it can be installed alongside Firefox or any other browser. No phoning home — Embedded server links and other calling home functions are removed. In other words, minimal background connections by default. User settings updates Extensions firewall: limit internet access for extensions. Multi-platform (Windows/Linux/Mac/and soon Android) Community-Driven Dark theme (classic and advanced) LibreWolf privacy features: Delete cookies and website data on close. Include only privacy respecting search engines like DuckDuckGo and Searx. Include uBlockOrigin with custom default filter lists, and Tracking Protection in strict mode, to block trackers and ads. Strip tracking elements from URLs, both natively and through uBO. Enable dFPI, also known as Total Cookie Protection. Enable RFP which is part of the Tor Uplift project. RFP is considered the best in class anti-fingerprinting solution, and its goal is to make users look the same and cover as many metrics as possible, in an effort to block fingerprinting techniques. Always display user language as en-US to websites, in order to protect the language used in the browser and in the OS. Disable WebGL, as it is a strong fingerprinting vector. Prevent access to the location services of the OS, and use Mozilla's location API instead of Google's API. Limit ICE candidates generation to a single interface when sharing video or audio during a videoconference. Force DNS and WebRTC inside the proxy, when one is being used. Trim cross-origin referrers, so that they don't include the full URI. Disable link prefetching and speculative connections. Disable disk cache and clear temporary files on close. Disable form autofill. Disable search and form history...and more. LibreWolf 152.0-1 changelog: Upstream release, see the Firefox 152.0 Release Notes Notable changes: The AppImages are now built on Codeberg along with the other releases We have decided to wait a bit longer to enable the settings redesign, due to use being aware of multiple upstream issues Download: LibreWolf 64-bit | Portable 64-bit | ~100.0 MB (Open Source) Download: ARM64 | Portable ARM64 Links: LibreWolf Home Page | Addons | Screenshot | Reddit Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
    • One Month Later
      eurospharma62 earned a badge
      One Month Later
    • Week One Done
      With What earned a badge
      Week One Done
    • Week One Done
      Harris Gilbert earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      560
    2. 2
      +Edouard
      169
    3. 3
      PsYcHoKiLLa
      73
    4. 4
      Michael Scrip
      64
    5. 5
      ATLien_0
      64
  • Tell a friend

    Love Neowin? Tell a friend!