Closed Bug 4387 Opened 26 years ago Closed 26 years ago

many pages render very slowly

Categories

(Core :: Layout, defect, P3)

x86
Windows 95
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: dbaron, Assigned: pollmann)

References

Details

In viewer from the mozilla.org builds of 99-03-24 (??), 99-03-26, and 99-03-29 (before it brought the whole system down in flames), many pages are rendered very slowly. For example, I see the problem on all mozilla.org bug pages, such as the one you will view this bug in (if you're not reading it by email). What happens is the page starts to load, all the form widgets show up in a reasonable time, and then the text in the page doesn't show up for another 5-10 sec. Some pages without forms render slowly as well, I think. I'm not sure if all do, because I don't have the 03-24 or 03-26 builds anymore, and 03-29 is *very* unstable (and messes up all the fonts in memory on the system before crashing).
if scrolling the page (in very large steps) after it has loaded results in similar slowdowns to the initial display described here, then this is a rendering issue, else it belongs to layout/style/parser/netlib.
Assignee: michaelp → troy
Component: Compositor → Layout
It's not related to scrolling. It's just initial load. Therefore, based on what you said, I'm assigning this to troy and changing component to Layout. On another note, Bugzilla pages are crashing in the 99-04-05 build. I haven't checked more recent ones.
Assignee: troy → pollmann
Eric, this sounds exactly like the problem we talked about today with SELECT elements
*** Bug 4717 has been marked as a duplicate of this bug. ***
Status: NEW → ASSIGNED
Most likely it is. Any page with a <SELECT> is affected. (The more <SELECT>'s the worse off we were). I've got a fix for this, and am trying to get it in to M4.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Target Milestone: M4
Just checked in a fix.
*** Bug 4581 has been marked as a duplicate of this bug. ***
Status: RESOLVED → VERIFIED
Verified Fixed.
You need to log in before you can comment on or make changes to this bug.