Closed Bug 94732 Opened 24 years ago Closed 24 years ago

Rendering takes ages on reload

Categories

(Core :: Layout, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: markushuebner, Assigned: waterson)

References

()

Details

(Keywords: ecommerce, perf)

Just visited the page http://www.world-direct.com/mozilla/ts.htm and see mozilla (build 2001081003) taking ages to render the page. Also disabled JavaScript which just had a little speed improvement.
Keywords: nsCatFood, perf
When just starting mozilla and loading this URL rendering speed is fine but when doing a reload it takes ages to display it again.
Can this be in connection with a cache problem?!
Summary: Rendering takes ages → Rendering takes ages on reload
updating keywords
reassigning to waterson.
Assignee: karnaze → waterson
Seems mostly fine for me (my connection to the site is on the slow side), except that on reload the last two images in the bar near (but not at) the top ("ANMELDUNG" and "MEIN KONTO"), or occasionally a different two images in that bar, never finish loading.
Please do a "SHIFT-RELOAD" than you see what I mean.
I did, and it didn't seem that bad. Is the problem that we're pegging the CPU or is the problem that we're slow to pull stuff off the netwerk? Could this be related to the bug that we keep too many persistent connections to a server alive at once?
From time to time you need to do several "shift-reloads" to see the 'effect'. It also happened that mozilla stopped loading and broke the page.
I'm not able to reproduce the problem on a fast connection. If you can narrow it down, please re-open the bug.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
I am sitting a few meters away from this server, being connected through a fiber optics line. So it's not a lame connection. Using build 2001083103 it's not that bad, has been considerably been improved since the day of reporting (2001-08-10). It still needs more time than IE especially until all elements are rendered fully but will verify for now.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.