Closed Bug 87668 Opened 25 years ago Closed 25 years ago

Page loads VERY slow, blocks other windows, displays wrong

Categories

(Core :: DOM: HTML Parser, defect)

x86
All
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 84466

People

(Reporter: jens-uwe, Assigned: karnaze)

References

()

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.1+) Gecko/20010624 BuildID: 2001062421 the page mentioned above takes 45 seconds to render on a P3-550 with 256MB of RAM (Linux). In this time it blocks the rest of mozilla completly. On the bottom of the page some news are not displayed (only the point before it). Please note, that this is already improved behaviour, older builds and NS6.1pr1 seem to hang completly on this page. Reproducible: Always Steps to Reproduce: 1. go to www.sciam.com/news 2. wait, try to go to other mozilla windows Actual Results: 1. it takes arround 45 seconds to render the page 2. during rendering it locks all other windows 3. on the bootom of the page the news are not siplayed correctly (different bug?) Expected Results: 1. it should render faster (main topic of this bug) 2. while rendering the other windows should be usable (bug 76722?) 3. it should render the page correctly (should I file a new bug?) the rendering hangs completly on NS6.1pr1, so it improved in the 0.9.2 cycle.
I see the same behavior, Win98, build 2001062504.
enter the following in the URL bar after the page finished to render: javascript:alert(document.documentElement.innerHTML.length); and the browser answers you: 1472353 I heard this is the namber of bytes after parsing and converting back to HTML. Since the original source code is only 100K long, this is IMHO way too much. Moving from Layout to parser, since parser probably fits better.
Component: Layout → Parser
DUP bug 84466 *** This bug has been marked as a duplicate of 84466 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
yepp, its a dupe. did not find it because the same url is spelled differently...
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.