Newer versions v slow to load pages. Reverting to 3.6
Why is it that when I upgrade from 3.6x to something like version 10, the page loading time increases by up to 30 seconds? I have reverted to 3.6.28, and get a much faster response time.
所有回覆 (8)
Did you try to test with a new Firefox profile? http://support.mozilla.org/en-US/kb/Managing-profiles Make a try and see if it's faster with FF12 than 3.6 (that's EOL now).
Thanks for the idea. I think I may have tried that already. I have two profiles set up - one with no extensions, and one with loads. I am pretty sure both of them were running slowly under FF 10/11.
Now that I've reverted, I can't tell what the problems were!
A possible cause is security software (firewall,anti-virus) that blocks or restricts Firefox or the plugin-container process without informing you, possibly after detecting changes (update) to the Firefox program.
Remove all rules for Firefox and the plugin-container from the permissions list in the firewall and let your firewall ask again for permission to get full unrestricted access to internet for Firefox and the plugin-container process and the updater process.
See:
Oh, that's even more interesting! But my security features/settings have not changed since sometime before the point I started using FF10/11.
Is the plug-in container itself a possible source of delay? I've wondered what the plug in container is about - as it often shows up pretty high on the memory consumption list of processes.
This is beginning to look more like it. I clamp down quite hard on Flash, try to restrict Java and JS, and don't use Silverlight or QT at all. I have had extensions to help do that, so I wouldn't be surprised if something was keeping the plugin container from doing something, which in turn might cause the page loading delays. The pages you point to talk about ways of blocking plugins from using the container, so I might have got somewhere by disabling that use. I am wondering if the container itself can be disabled without affecting the main program. Is that what setting dom.ipc.plugins.timeoutSecs to -1 does?
Ooop. Got that wrong. I should have said dom.ipc.plugins.enabled. That's the one which apparently disables the container.
Disabling plugin container may or may not help with troubleshooting your problem, but it is relatively easy to enable and disable as you appear to have discovered.
You are already using multiple profiles. You could also consider for comparison/test purposes running multiple versions of Firefox. You may normally wish to avoid using EOL versions but it is easy to run multiple Firefox versions as long as each has its own profile.