How is version 60 ("Nightly") in comparison to 59.0b6 (64-bit), especially in terms of memory use?

How stable is 60 lately? I haven't much paid attention lately, so just looking for general impressions. The only extensions which interest me are broken anyhow (Adblock Plus, Context Search, Session Manager), so if 60 is no worse there, and better in other areas, I'll consider testing that out.

Nightly has been very stable for me on Linux. There have been some annoyances (not always minor) but it has been at least a couple of years since I needed to switch to another branch temporarily for my regular (non-testing) browsing.

Adblock Plus may be working, but I shut off all extensions, because things are kind of spotty with this version. I'm beginning to wonder if it is because I only have 4Gb of RAM. This is why I was asking if there are any memory improvements. Thanks for your feedback.

A few versions of Nightly ago (last August or September?) I was having issues with AdBlock Plus and ended up switching to uBlock Origin. (The problem was the member home screen for http://www.netflix.com: some bug was causing CPU to run full bore so the page would take almost a minute to render. The issue might have since been fixed.)

With some of the pages I visit (particularly my overly large Netflix DVD Queue), I'm glad I went with 8GB RAM in this machine, but I can launch a second browser without issue (as long as I am not displaying my Netflix DVD Queue in more than one of them) and I often do when I am looking at issue or writing instructions for Beta or Release versions or a side-by-side comparison of Firefox and Chrome. (I was surprised how different AdBlock Plus was between the Firefox build and the Chrome build.)

The times I have looked at the Task Manager and had just Firefox Nightly up and running and was not displaying my Netflix DVD Queue or a long ways down an infinitely expanding page, total memory usage was under 4GB. (E. g., right now it's sitting at 3.54GB.)

The times I have looked at the Task Manager and had just Firefox Nightly up and running and was not displaying my Netflix DVD Queue or a long ways down an infinitely expanding page, total memory usage was under 4GB. (E. g., right now it's sitting at 3.54GB.)

I am always amazed when I see users here talk about high Firefox memory usage. I don't have a Netflix account so I don't have your queue so I can't try that but sitting here, right now, logged onto this site Firefox Nightly is only using 297 MB of ram.

DN123ABC wrote:I'm on Windows 7. and it is "Processes" or "Performance".

Under "Processses", it lists for Firefox:336,908K298,344K204,528K138,212K

and those things are cranking up pretty fast!

Without seeing your display I would "guess" the 336 number is Firefox and the others are the child processes running it the other cores of you CPU. As for cranking up? That is normal as 'things' run in the other cores by design.

malliz wrote:And as far as I know you have been told that's not true. How about NOT taking nightly build threads off Topic?

I'm saying it is true, and it is TOTALLY on topic. The topic is which version to run. This is the "builds" area, right? I've been signed up and testing Firefox since Phoenix, so I know a little bit about this.

"A really, really, relevant check to add for 64-bit _migration_ would be instead memory consumption average/Xpercentile. Or perhaps more specifically if this multiplied 1.5x is less than 50% of installed RAM. Ie: my use-case is that I have 4GB installed, and FF on *average* uses 2. (Unless bug 1125557 lands anytime soon) I think it's pretty glaring that I'd be screwed with x64. "

As you can see from the results in all 11 tests above, the 32-bit version of Firefox won an impressive 8 of the tests, only losing its number one position in the Kraken and Peacekeeper benchmarks and the cold start time. The memory usage results were also better and if you scale them up, the differences between 32-bit and 64-bit versions with multiple large website tabs open could be hundreds or even thousands of Megabytes.Read More: https://www.raymond.cc/blog/mozilla-fir ... -to-32bit/