Here is another weird thing. Downloading, everything slows to a halt - FF at least. You can't open another site without a 5-10 second delay. Then after a short period speed falls from the normally scintillating tiscali 120k to around 5k. Gradually.
Is this sounding like memory leak?
Peter
Hi,
2008/10/31 Peter Alcibiades palcibiades-first@yahoo.co.uk:
Here is another weird thing. Downloading, everything slows to a halt - FF at least. You can't open another site without a 5-10 second delay. Then after a short period speed falls from the normally scintillating tiscali 120k to around 5k. Gradually.
Bad FF3 download code? Throttling by Tiscali? Normal TCP congestion handling kicking in?
Is this sounding like memory leak?
Excuse me? Why would you think this is a memory leak?
Srdjan
2008/10/31 Peter Alcibiades palcibiades-first@yahoo.co.uk:
Here is another weird thing. Downloading, everything slows to a halt - FF at least. You can't open another site without a 5-10 second delay. Then after a short period speed falls from the normally scintillating tiscali 120k to around 5k. Gradually. Is this sounding like memory leak?
Only if your whole system slows down. FF3 on Ubuntu 8.04 works just fine for me.
Tim.
Hi,
2008/10/31 Tim Green timothy.j.green@gmail.com:
2008/10/31 Peter Alcibiades palcibiades-first@yahoo.co.uk:
Here is another weird thing. Downloading, everything slows to a halt - FF at least. You can't open another site without a 5-10 second delay. Then after a short period speed falls from the normally scintillating tiscali 120k to around 5k. Gradually. Is this sounding like memory leak?
Only if your whole system slows down.
Why?
If you are leaking 50 bytes per minute. And you started leaking 10 minutes ago, you would have leaked 500 bytes. It's still a memory leak, but it is unlikely your machine would have run out of RAM for the kernel to start thrashing (to get you more pages) or to invoke the OOM-Killer.
The opening of another "site" delay might be due to the firefox process being busy processing something. Perhaps that's the main part of the problem. But that's not a memory leak in itself.
I've found that on some sites, you can open a new tab in FF2 very quickly. But if you do: ctrl-t, slashdot.org, ctrl-t, (some other site)
the last tab takes a long time to draw and load due to the new Web 2.0-ish slashdot. Do it with some other site and it's faster.
Maybe we need threaded tabs in FF.
Srdjan
-
Peter Alcibiades -
Srdjan Todorovic -
Tim Green