3 ms·

Long long time FF/Navigator user at this point mostly by inertia. The biggest issue I have (forever) is FF is a memory pig that eventually becomes sluggish. Th

by beezle 6y ago

Long long time FF/Navigator user at this point mostly by inertia. The biggest issue I have (forever) is FF is a memory pig that eventually becomes sluggish. Though I do have a lot of tabs in four windows, I've set prefs so it only loads tabs when I click on them. So in reality I have a lot fewer tabs "active" on any given day. Yet I regulary see memory use grow from an initial 600MB to 4 or 5GB. FF seems not to properly release memory back, in particular after new tabs with video are closed. I might live with it were it not for the eventual slowdowns.

bartvk 6y ago
This is definitely not normal. Have you checked about:memory
MayeulC 6y ago
You might be "relieved" to learn that Google Chrome/Chromium is almost universally considered heavier on RAM. This might partly be due to the "one tab, one process" architecture. Of course, if you are experiencing a memory leak in Firefox, that's another story... But I can usually trace that to a memory leak in some heavy javascript "application" I have open.
- seba_dos1 6y ago
  Oh yes, Chromium is simply not capable of supporting tab-intensive workflows that Firefox handles without issues. It becomes completely useless after just a few dozen open tabs, from both UX and performance perspectives.
- iggldiggl 6y ago
  > This might partly be due to the "one tab, one process" architecture. With site isolation/"Fission" it looks like this isn't going to get any better in Firefox, either, as they'll have to move to "one domain/origin, one process", which could be even worse in terms of memory overhead due to the number of separate processes required.
mccr8 6y ago
We fix memory leaks when people report them and we can reproduce them. Usually it is due to some combination of particular addons and particular websites, but of course the obscurity of any particular leak doesn't help you if you are hitting it regularly.

by beezle 6y ago

bartvk 6y ago

This is definitely not normal. Have you checked about:memory

MayeulC 6y ago

You might be "relieved" to learn that Google Chrome/Chromium is almost universally considered heavier on RAM. This might partly be due to the "one tab, one process" architecture. Of course, if you are experiencing a memory leak in Firefox, that's another story... But I can usually trace that to a memory leak in some heavy javascript "application" I have open.

seba_dos1 6y ago
Oh yes, Chromium is simply not capable of supporting tab-intensive workflows that Firefox handles without issues. It becomes completely useless after just a few dozen open tabs, from both UX and performance perspectives.
iggldiggl 6y ago
> This might partly be due to the "one tab, one process" architecture. With site isolation/"Fission" it looks like this isn't going to get any better in Firefox, either, as they'll have to move to "one domain/origin, one process", which could be even worse in terms of memory overhead due to the number of separate processes required.

mccr8 6y ago

We fix memory leaks when people report them and we can reproduce them. Usually it is due to some combination of particular addons and particular websites, but of course the obscurity of any particular leak doesn't help you if you are hitting it regularly.