micky wrote:
> VanguardLH wrote:
>
>> micky wrote:
>>
>>> With 4 gig, using task manager I could get up to about 1.7gigs in
>>> use by Firefox, so of course with 4 more gig, I should be able to
>>> go up to 5.7gigs, right? Wrong.
>>
>> "Windows XP" without any bitwidth qualifier means the 32-bit
>> version,
>
> Yes, that's what I meant.
>
> The OS is 64-bit, but I had trouble with the 64-bit version of FF so
> I'm using 32-bit there.
You are posting in a Windows XP newsgroup. When queried for bitwidth,
you said you were using Windows XP 32-bit. Now you say you are using
the 64-bit version of Windows XP. Which is it? You first mentioned
your laptop and then your desktop. Is the laptop running 32-bit WinXP
and the desktop running 64-bit WinXP?
64-bit WinXP has always been more flaky as it is a frankenjob OS.
32-bit applications that run on 32-bit WinXP fail on 64-bit WinXP.
64-bit applications that run on 64-bit Windows 2003 Server fail on
64-bit WinXP. 64-bit WinXP was Microsoft trying to catch up but late on
providing a 64-bit platform and did so poorly.
The 2 GB max user-mode memory space per process and 3 GB memory for all
user-mode processes is a limitation of the 32-bit version of Windows XP
(or any 32-bit version of Windows).
>>> A while back I had the feeling that tabs would unload when you
>>> clicked on another tab,
>>
>> Why?
>
> "Because" started the next sentence.
You were describing an effect, not the cause. Firefox isn't unloading
the tabs. More likely the add-on(s) you installed are doing that unless
the real problem is a very slow drive or something slowing down access
to the web cache.
Have you tried rebooting Windows into its safe mode (with networking)
and load Firefox in its safe mode to retest if the momentary delay on
refocusing on a tab still results in a lag in repainting the page? This
won't resolve hardware issues but will eliminate startup programs and
addons from causing the problem.
> I don't know the internals, but maybe the page was put on the HDD.
If that's the storage medium in your computer then that is where the web
cache is stored. Go to about:cache to see Firefox's cache statistics.
If there are cached entries, you'll see a link to list them.
If you don't want Firefox to purge its local data (cookies, web cache,
DOM storage, etc) upon its exit so all that data lingers around until
your next Firefox session, you can use an add-on to let you determine if
and when to purge Firefox's local data during a Firefox session. I do
not have Firefox retain any local data after a web session. I have
Firefox purge ALL of its local data upon exit.
>>> It would be a good thing to do that if that freed up ram and delayed
>>> freezing,but I dont' think I've seen that lately and maybe that
>>> wasnt' true.
>>
>> There are add-ons to unload tabs, like OneTab. There was another
>> one but been too long since I last looked at it.
>
> I'll look into OneTab. It might help. Even if it slows things down,
> if it prevents freezing that's a net gain in time. Thanks.
My recollection of OneTab is that you had to select a tab to unload.
You clicked on its toolbar icon to unload tabs and provide a list to let
you reload them. It's also a legacy extension which means it won't
survive with FF57; however, you're on Windows XP which means the latest
you can use there is FF52ESR. I've never used Session Manager (also a
legacy extension) to know if it has an auto-unload feature for tabs. It
certainly has a tons of features. Tab Suspender says it will
automatically unload inactive tabs. Obviously an unloaded tab will take
time to reload; however, some of the web page will be in the web cache
and not have to get re-retrieved. There are several tab auto-unload
extensions. I've never used any of them.
An unloaded tab (if YOU choose to unload them) will take time to
re-retrieve the page again from the server when you focus on the
unloaded tab. A cached web page should be nearly instantly repainted
when you refocus on an unloaded tab and a still-loaded tab should
already still be painted so there is no lag to show that tab. That
there is a lag to show the web page (whether to re-retrieve from server
or reread the web cache) means something unloaded the tab.
With tons of tabs open, could be that Firefox is unloading the oldest
tabs to conserve on memory (not disk space for the web cache). It only
has so much system RAM it gets to use.
Some tweaks you can try:
- In about:config, set network.prefetch-next = False. When Firefox
loads a page, it also goes out to all the linked resources in a web
page to shove them into its web cache. All that downloading takes
bandwidth (and more than you intended when selecting a specific web
page to visit) which means more time. The downloading is in the
background so you're supposed to not see it but you are loading LOTS
of tabs and each of those pages could be pre-fetching content. It
also defeats ad and tracking blockers by retrieving a resource that
you would've blocked if it had been retrieved by the current document
(web page). Pre-fetching resources means you touched those resources
which can then track from where you came. See:
https://en.wikipedia.org/wiki/Link_prefetching#Issues_and_criticisms
- Every tab has its own history. When you use the same tab to visit
other pages or sites, like clicking on hyperlinks or using the address
bar, a history is maintained during the life of that tab. That's why
you can click on the Back button to look at history for a tab. The
default history for a tab is 50 entries. Do you really need to
revisit something that far back? If so then why are you opening so
many tabs? More history is a load on Firefox to maintain per tab.
In about:config, set browser.sessionHistory.max_entries to 10 (instead
of the default of 50) to reduce load on Firefox for history.
- What is the value for the browser.cache.memory.enable setting? See
http://kb.mozillazine.org/Browser.cache.memory.enable. True makes
Firefox reload pages faster.
- While Mozilla added a new HTTP cache (aka cache2) that is supposed to
be faster and more streamlined (seems mostly the latter as it helps
halts in Firefox but doesn't seem to do much for increasing speed),
they decided for some reason to disable it by default. Go into
about:config and check the browser.cache.use_new_backend setting.
Mine is 0 (disabled). Change to 1 to enable. This was introduced
back around 2014. I don't know why it is not enabled by default.
Seems an overly long time to still be considered an experiment.
NOTE: I went into about:cache and the disk cache location is the
cache2 folder. My guess Mozilla went full ahead on their new cache
it is ignored.
- Make sure the Flash plug-in is configured for "Ask to Activate" to
NOT start playing streamed Flash content in a web page until YOU allow
it. You don't need to be loading tons of tabs, especially in the
background where you won't see them, to have Flash playing in many of
them. Or just disable the Flash plug-in (improve security, make sites
use HTML5 <video> if they have both content types).
- If you don't even want HTML5 <video> to start playing and consume
bandwidth for a tab opened in the background, go into about:config and
change media.autoplay.enabled to False. However, some sites won't let
you manually start playing their video as they provide no user
controls in the UI for their player. Don't remember the domain but
users complained about some movie site not letting them manually start
playing the movie videos there. For those sites that provide no user
controls (buttons for Play, Pause, etc), sometimes you can right-click
on the video to select Play. Even when there is a Play button shown,
sometimes it requires clicking it twice. If you want to disable
auto-play for HTML5 <video> only for background tabs (i.e., you
configured Firefox to open new tabs in the background), set
media.block-play-until-visible to True (unnecessary if already
media.autoplay.enabled is False).
- Check if Electrolysis (e10s) is enabled. This is the new
multi-process scheme for Firefox. Go to about:support and search on
"multiprocess". If it is "1/1" then it is enabled. If it is "0/1"
then you have an add-on that interferes with the use of e10s. I
replaced all my legacy add-ons with WE (WebExtension) version, except
for uMatrix that I'm still waiting for its WE release (its beta
version is unuable due to uncontrollable scrolling of its table);
however, even with legacy uMatrix I'm getting "1/1". You should also
see in Options -> General tab a new Performance section where the
number of content processes can be specified. Mozilla is starting
with 1 (although it may differ depending on your hardware). Going
higher means more memory consumption by Firefox. Mine is at 1.
I've read where some folks have changed it to 4. For some info, see:
https://www.ghacks.net/2017/05/27/firefox-54-multi-content-processes/,
https://www.ghacks.net/2016/02/15/change-how-many-processes-multi-process-firefox-uses/.
You have to disable the "Use recommended" option to see the separate
options for hardware/GPU acceleration and content process limit.
Mozilla recommends changing from the recommended default only if you
have more than 8 GB of system RAM. My desktop is 8 GB. I'll try it
at 4 for awhile to see if I notice any performance gain. If not, back
to 1. Changing this value requires a restart of Firefox. More
content processes means more memory consumption, something you already
noted having a problem.
- I usually exit Firefox when I'm not using it. Some folks want to
leave it running it all the time; i.e., the Web is their primary use
of their computer. When Firefox is left running but you minimize it
(to do something else, God forbid), it does not reliniquish any of its
resources, like GUI objects. That means it uses as much memory
whether its window is display or when hidden (and all you have is the
taskbar button). To reduce memory consumption when you hide its
window, create a new Boolean variable named config.trim_on_minimize
and set to True. See:
http://kb.mozillazine.org/Config.trim_on_minimize.
Since I don't leave Firefox running when I'm not using it, this
setting is inapplicable to me.
- How big is the web cache (Options -> Advanced -> Network -> Cached Web
Content)? The idea is to locally cache the web pages so they can get
reloaded quicker than having to re-retrieve them from the server. For
me, I purge everything on exit from Firefox so I don't need a huge web
cache. I configured it to 500MB maximum. I would've set it to zero
since I have an always-on high-speed broadband connection but some web
cache is okay per Firefox session. The bigger the web cache to more
time to maintain it. There is also the problem of having to check if
the page has been modified since the content was stored in the web
cache, and not all pages provide a Modified datestamp or it is never
updated which results in re-downloading the page anyway. Then there
is all that head seeking on the hard disk. If you have an SSD, a web
cache means more wear that shortens its life. For a fast Internet
connection and since I changed to an SSD for the OS partition, I'll
go back to disabling the web cache (set the override from 500MB to
zero) which also means less time to do the purge on exit. I actually
prefer the web browser retrieve a web page anew instead of having to
piece together what is current versus what is old to then now what has
to be retrieved that is changed. I get a new web page upon visit. I
still have to allow DOM Storage (aka Offline Website Data) because
I've hit too many sites that require it for their page to be
functional but it does get purged on Firefox's exit.
- Go to about:memory and click on "Minimize memory usage". That is only
a very temporary solution. If there's nothing available to free then
there won't be any reduction.
- Is hardware (GPU) acceleration enabled in Firefox? It can speed up
Firefox but only at web sites that use graphical rendering (e.g.,
online 3D games). It can cause Firefox to crash because either the
hardware (GPU's firmware) or especially the video driver won't support
it. You could enable it to see if you get faster page rendering in
Firefox. You could disable it to see if those Firefox crashes go
away.