Micky
2016-04-27 13:28:47 UTC
[Default] On Mon, 25 Apr 2016 16:05:22 -0500, in
moderated. I was told about 15 years ago that if one posted to a
moderated and unmoderated group at the same time, the post wouldn't
reach the unmoderated one until it had passed moderation.
But what happened this time was that it never showed up in the mozilla
group and I had to post there separately. At least I was going to do
that, but maybe the answers I got here were enough that I thought the
mozilla folks couldn't do any better.
me.
So I took Firefox out of the list just now.
that you installed into Firefox. Some of them perform updates. No, I
do not mean updates for the add-on code itself. I'm talking about
getting updates to data that the add-on uses. For example, the adblock
add-ons will need to check if there is a newer version of their block
lists.
Also, some add-ons will slow the load of Firefox. Add-ons store their
block lists into memory and why adding more subscribed block lists in an
adblocker results in consuming more memory. Takes time to read from the
slow hard disk those tables of block lists into memory.
Typically the add-on updates (to the add-ons themselves and for them to
get newer data) is short-lived. The longer time to load large block
lists and a larger number of them into memory occurs only when you load
Firefox; i.e., they affect load time for Firefox. Since this is not
what you describe but rather a constant high CPU usage, I would start by
loading Firefox in its safe mode, or disable all extensions and reload
Firefox. Then see if the firefox.exe process alone (without any child
threads for add-ons) is still sucking up the CPU.
When you "close" Firefox, has it actually unloaded? Load Task Manager
and watch its Processes tab. Load Firefox and, in Task Manager, select
to highlight the firefox.exe process. Then exit Firefox. How long
before the firefox.exe process disappears? Anything over 5 seconds is
too long for Firefox alone and hints that you have an add-on that
doesn't exit properly or does something on exit that takes a long time,
like it performs some cleanup actions that take time.
If you visit web pages with Flash content, and allow it, then Firefox
loads that plug-in inside its sandbox: plugin-container.exe. That
sandbox does occasionally hang on exiting Firefox. You may eventually
get a popup telling you that plugin-container.exe has crashed but not
always (it may simply hang instead of crash). You said that you were
loading Firefox with about:blank pages, not that you had visited sites
with Flash content. If you are visiting Flash-enabled web sites, look
in Task Manager to see if the plugin-container.exe process got loaded.
Then exit Firefox to see if plugin-container.exe hangs around although
the firefox.exe process disappeared. Sorry but I don't know of a way
(within Firefox) to force termination of its plugin sandbox on exit from
Firefox. I have yet to find an out-of-process add-on (the add-on, when
it loads because Firefox loaded, will start an out-of-process monitoring
program) that will monitor for an exit action from Firefox to then
ensure after some expiration interval that firefox.exe and
plugin-container.exe have truly unloaded.
Actually you said you had 1 tab open to a "blank search page". Whose
search? Have you tried configuring Firefox so your home page is
about:blank so you do load a blank page instead of running some script
at some search site? With extensions disabled (or using Firefox's safe
mode) and with the home page set to about:blank, use Task Manager to
ensure there are no lingering firefox.exe or plugin-container.exe
processes. Then load Firefox and exit it to see if firefox.exe is still
lingering around for more than a few seconds.
Start with loading just one tab to note CPU usage by firefox.exe. With
20 tabs open, cleanup could take awhile depending on what purge-on-exit
options you configured in Firefox and how big is its web cache. (I run
with a zero-sized web cache and haven't noticed any lag in connecting to
web sites and downloading and rendering their pages.)
Wow. Thanks a lot. I've read this once already, and I'll read it
again. It fills in some big holes, bigger than I thought they were,
in my understanding of all this.
mozilla.support.firefox (+)
alt.windows7.general (*)
microsoft.public.windows.vista.general
microsoft.public.windowsxp.general (*)
Actually, I didn't think this would work, because the mozilla group isalt.windows7.general (*)
microsoft.public.windows.vista.general
microsoft.public.windowsxp.general (*)
moderated. I was told about 15 years ago that if one posted to a
moderated and unmoderated group at the same time, the post wouldn't
reach the unmoderated one until it had passed moderation.
But what happened this time was that it never showed up in the mozilla
group and I had to post there separately. At least I was going to do
that, but maybe the answers I got here were enough that I thought the
mozilla folks couldn't do any better.
(*) Mickey does not declare the problem exists on Windows 7 or
Windows XP so his post there is off-topic. He only states
what happens on his Windows Vista setup. Different software
environs can produce different effects.
(+) Chris Ilias often rejects my posts in the Firefox newsgroup.
So my reply may only show up in the non-Mozilla newsgroups.
It did, but mostly, I think, for the same reason it didnt' show up forWindows XP so his post there is off-topic. He only states
what happens on his Windows Vista setup. Different software
environs can produce different effects.
(+) Chris Ilias often rejects my posts in the Firefox newsgroup.
So my reply may only show up in the non-Mozilla newsgroups.
me.
So I took Firefox out of the list just now.
Why is FFox at 50% cpu when only one tab is open and it has a blank
search page?
I'm using winVista but it's a lot like 7.
Firefox was slow, so I opened a new window with only one tab, and
closed the window with 20 tabs (most of them still not loaded after a
restart), and I still get Not Responding for Firefox.
I have almost no internet traffic (just some for my small webradio
player), barely any reading or writing to the disk, Sessionstore
completed being saved 7 minutes ago, I'm only using 81-84% of my RAM,
NO hard faults, but Firefox is using 50% of the CPU. And has been
for 9 minutes since I closed that FF windows.
And why does it stay at 49-50%? How come it doesn't go up higher to
do what it needs to do (since barely anything else is running), or
vary more than a percent.
When you load Firefox, you also load all the active extensions (add-ons)search page?
I'm using winVista but it's a lot like 7.
Firefox was slow, so I opened a new window with only one tab, and
closed the window with 20 tabs (most of them still not loaded after a
restart), and I still get Not Responding for Firefox.
I have almost no internet traffic (just some for my small webradio
player), barely any reading or writing to the disk, Sessionstore
completed being saved 7 minutes ago, I'm only using 81-84% of my RAM,
NO hard faults, but Firefox is using 50% of the CPU. And has been
for 9 minutes since I closed that FF windows.
And why does it stay at 49-50%? How come it doesn't go up higher to
do what it needs to do (since barely anything else is running), or
vary more than a percent.
that you installed into Firefox. Some of them perform updates. No, I
do not mean updates for the add-on code itself. I'm talking about
getting updates to data that the add-on uses. For example, the adblock
add-ons will need to check if there is a newer version of their block
lists.
Also, some add-ons will slow the load of Firefox. Add-ons store their
block lists into memory and why adding more subscribed block lists in an
adblocker results in consuming more memory. Takes time to read from the
slow hard disk those tables of block lists into memory.
Typically the add-on updates (to the add-ons themselves and for them to
get newer data) is short-lived. The longer time to load large block
lists and a larger number of them into memory occurs only when you load
Firefox; i.e., they affect load time for Firefox. Since this is not
what you describe but rather a constant high CPU usage, I would start by
loading Firefox in its safe mode, or disable all extensions and reload
Firefox. Then see if the firefox.exe process alone (without any child
threads for add-ons) is still sucking up the CPU.
When you "close" Firefox, has it actually unloaded? Load Task Manager
and watch its Processes tab. Load Firefox and, in Task Manager, select
to highlight the firefox.exe process. Then exit Firefox. How long
before the firefox.exe process disappears? Anything over 5 seconds is
too long for Firefox alone and hints that you have an add-on that
doesn't exit properly or does something on exit that takes a long time,
like it performs some cleanup actions that take time.
If you visit web pages with Flash content, and allow it, then Firefox
loads that plug-in inside its sandbox: plugin-container.exe. That
sandbox does occasionally hang on exiting Firefox. You may eventually
get a popup telling you that plugin-container.exe has crashed but not
always (it may simply hang instead of crash). You said that you were
loading Firefox with about:blank pages, not that you had visited sites
with Flash content. If you are visiting Flash-enabled web sites, look
in Task Manager to see if the plugin-container.exe process got loaded.
Then exit Firefox to see if plugin-container.exe hangs around although
the firefox.exe process disappeared. Sorry but I don't know of a way
(within Firefox) to force termination of its plugin sandbox on exit from
Firefox. I have yet to find an out-of-process add-on (the add-on, when
it loads because Firefox loaded, will start an out-of-process monitoring
program) that will monitor for an exit action from Firefox to then
ensure after some expiration interval that firefox.exe and
plugin-container.exe have truly unloaded.
Actually you said you had 1 tab open to a "blank search page". Whose
search? Have you tried configuring Firefox so your home page is
about:blank so you do load a blank page instead of running some script
at some search site? With extensions disabled (or using Firefox's safe
mode) and with the home page set to about:blank, use Task Manager to
ensure there are no lingering firefox.exe or plugin-container.exe
processes. Then load Firefox and exit it to see if firefox.exe is still
lingering around for more than a few seconds.
Start with loading just one tab to note CPU usage by firefox.exe. With
20 tabs open, cleanup could take awhile depending on what purge-on-exit
options you configured in Firefox and how big is its web cache. (I run
with a zero-sized web cache and haven't noticed any lag in connecting to
web sites and downloading and rendering their pages.)
again. It fills in some big holes, bigger than I thought they were,
in my understanding of all this.
