why does firefox 6 get too slow browsing when browse about 15 sites opened with Morning Coffee (add-on) not in firefox 5.0.1
when i open about 15 sites in firefox 6.0 and 6.0.1 with Morning Coffee Add-on version 1.35 it's get too slow to browse all of them It takes about 30min or more some time never load sites but when i do it in firefox 5 , 5.0.1 Or 3.x.x it's speed of browsing is good and take about 2 to 3 min to browse completely all of them. i think there is some problem with multiple tab browsing in firefox 6 Or maybe a security that makes it slow to browse many sites. Please Help
Променено на
Избрано решение
Firefox 8 solve this problem.!
Прочетете този отговор в контекста 👍 0Всички отговори (5)
I've had this problem too and it is not only when I use Morning Coffee, it is any time I open more than one or two tabs. It is extremely annoying. I eliminated the problem (at least for a while) by buying a newer and much faster PC and my sister just opted for the same solution. However, the problem is now back due to a hardware failure in my newer PC (I'm now waiting for a new power supply to be delivered).
The problem is that Firefox was developed using newer and faster PC's and the developers did not consider the needs of the less fortunate. Probably they were not even aware that many people still use anything but the latest PC's. However, I believe that the developers could fix the problem without too much trouble and we should all plead with them to make this a high priority - not everyone can afford a new PC.
I strongly believe that the problem is something known as page thrashing. It doesn't happen in newer PC's because the new ones usually have multiple gigabytes of RAM (my old clunker has only a couple megabytes and it is impractical to upgrade it into the Gigabyte range).
When you open up multiple tabs, Firefox sets to work on all of them with separate copies of itself (called tasks), spending a few milliseconds on one and then another. So long as you have enough RAM this works fine, but if not then each task has to be copied to disk and another loaded from disk. This copying out to disk and then reloading another task is time-consuming and it results in the PC being slowed down to a crawl. It takes forever to bring any one of the tabs up and all of that copying to and from disk may even cause a crash.
What to do? The Firefox developers need to introduce a configuration option to allow installations with smaller RAM to suspend the tasks associated with inactive tabs (i.e., tabs other than the one currently selected). Sure, when you switch to another tab it will take some time to come up, but that is by far preferable to slowing all tabs down to a crawl. The tabs are still very useful because they keep track of the sites you have decided to visit.
If the developers want to get fancy with this they could detect the amount of RAM that is available and set the number of allowed active tasks to a value that is appropriate - or even just suggest a value for the user in the configuration menu. I don't know the internals of Firefox, but none of this should be too difficult.
Thanks for your reply. but i think your wrong. it's a problem in loading tabs algorithm.
I think 2GB of RAM and a 3GHz core2duo CPU is enough for this simple task(browsing about 10-15 tabs) see the System Requirements for Firefox 6 here
if they need more of system resources they could change the system requirements. so you don't need to change or upgrade your PC.
please reply if i say wrong.
Again thanks for your reply!
If you check my earlier comment, my problem was with an older machine that has well below 2 GB of ram (to be precise, 256 MB). Can you suggest a browser that is appropriate for an old clunker like this?
I still do think that providing some way to disable inactive tabs would be useful.
sorry for that.
i don't have any inactive tabs so it can't be useful.
if you can post your new PC spec and describe how fast you can browsing multiple tabs with or without Morning Coffee add-on I'll appreciate you. thanks for your reply
Променено на
Избрано решение
Firefox 8 solve this problem.!