Closed Bug 87947 Opened 24 years ago Closed 21 years ago

Page reloads for http://sis.rpi.edu/f01rscha.htm are very slow

Categories

(Core :: Layout: Tables, defect, P3)

defect

Tracking

()

RESOLVED WORKSFORME
Future

People

(Reporter: jhatax, Unassigned)

References

()

Details

(Whiteboard: DUPME [awd:tbl])

The reload of this page by Mozilla is very slow when returning from any other page visited. This isn't the case in IE which reloads the page in a matter of seconds (approximately 2 seconds) while Mozilla takes a good 10-11 seconds for reload. I read the discussion on Save As, View Source, etc from bug 40867 about the memory requirements of Mozilla in case it were to store the source of the pages it has previously reloaded. Mozilla is a big memory hog even at this point in time (I use build 2001060703 though this bug is being posted using Netscape 4.x) and sure consumes more memory and CPU resources than does IE. Does anyone have a clue as to how IE does page reloads or how Mozilla's page reloads can be sped up.
I think that this is probably a dup. The html on this page is injured, it looks decapitated. but things should display faster. The problem is probably either in layout or the parser.
Status: UNCONFIRMED → NEW
Component: Networking: Cache → Layout
Ever confirmed: true
Whiteboard: DUPME
I forgot to note I'm seeing this with the latest June 26 cvs on w2k.
to default owner
Assignee: gordon → karnaze
QA Contact: tever → petersen
Whiteboard: DUPME → DUPME [awd:tbl]
This bug is still there. The reload times are quite slow. I'm not convinced its parser or layout at all. dup this to what by the way?
Temporarily moving to future until a milestone can be assigned.
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Another example of this bug is http://www.uwsg.iu.edu/hypermail/linux/kernel/ go to any day using a threaded view then click any article. Then go back to the threaded view using the back button. On IE this results in an instant page reload to your previous scroll position. In Mozilla or Galeon the page almost seems to reload every time and it goes to the top of the page until the entire page is loaded rather than going to the previous scroll position.
mass reassign to default owner
Assignee: karnaze → table
Status: ASSIGNED → NEW
Component: Layout → Layout: Tables
QA Contact: petersen → madhur
Target Milestone: Future → ---
Priority: -- → P3
Target Milestone: --- → Future
http://www.uwsg.iu.edu/hypermail/linux/kernel/ worksforme. The original page this was reported on does not exist. Is this still a problem?
Also WFM (1.7b, WinXP), I guess it should be resolved. Anyone opposed?
IMHO it's still too slow compared to IE, but this is not a tables problem since there aren't any tables on http://www.uwsg.iu.edu/hypermail/linux/kernel/ (except the Google search) and the following pages, just hundreds of <ul> and <li> tags. I'm not sure what the right component would be though, where's the bottleneck here?
Well, whatever it is, it's not this bug. Marking this one worksforme; please file separate bugs on separate problems (and make sure the problem exists in a current trunk build before filing).
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
I'm sorry if I put this bug in the wrong place, it was 2 years ago that I added my comment though! :P Btw, this is a lot better nowadays (Firefox 0.10.1) but it's still not as good as IE. I'll be a little more explicit in describing what I'm talking about. 1) Go to: http://www.ussg.iu.edu/hypermail/linux/kernel/0407.3/index.html (this is the same as I previously described, but looking at a specific year/month/day) 2) Scroll down about halfway down the page and click on an article (I'll click on: [PATCH 29/47] Add Audigy LS PCI ID to emu10k1-gp) 3) Press the back button 4) Notice: Firefox takes you to the top of the page until it's reparsed/rerendered/rewhatevered and then takes you back to where you were previously. In IE, it doesn't re-render the page and it takes you instantly back to the proper position without first visiting the top of the page.
You need to log in before you can comment on or make changes to this bug.