Closed
Bug 105621
Opened 23 years ago
Closed 23 years ago
Browser crash when visiting this URL
Categories
(Core :: DOM: HTML Parser, defect)
Core
DOM: HTML Parser
Tracking
()
VERIFIED
DUPLICATE
of bug 100263
People
(Reporter: will.morton, Assigned: harishd)
References
()
Details
(Keywords: hang)
I'm using Mozilla v0.9.5. When I visit the URL
http://www.vmware.com/support/ws3/doc/ws30_disks4.html the browser hangs and
jumps to 100% CPU utilization.
I turned off Javascript, but this didn't solve the problem.
Comment 1•23 years ago
|
||
confirming 2001101803 NT4
Mozilla hangs (100% CPU) before any rendering.
Memory use keeps growing --> finish to crash (did not try that)
Reporter | ||
Comment 3•23 years ago
|
||
Confirmed also on 2001101117/Win2kServer
Comment 4•23 years ago
|
||
I ran it through HTMLtidy, it gives more than 300 Errors, then the resulting
page displays fine. This is a very crappy Framemaker -> HTML conversion.
Based on the comment below this should actually be platform all/all I think.
Comment 5•23 years ago
|
||
Found the problem. The document has 33 Title tags scattered around the document.
Removing those fixes the problem.
Comment 6•23 years ago
|
||
this freezes me so i can't get a talkback report. Need someone with a debug build
Severity: major → critical
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: hang
OS: Linux → All
Hardware: PC → All
Comment 7•23 years ago
|
||
Moving them all to the <HEAD> section also fixes it.
But I'm unable to create a simplified testcase.
Confirmed on 2001080110, WinXP. Page mostly loads, freezing near the end.
Comment 9•23 years ago
|
||
->parser
Assignee: asa → harishd
Component: Browser-General → Parser
QA Contact: doronr → moied
Assignee | ||
Comment 10•23 years ago
|
||
*** This bug has been marked as a duplicate of 100263 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Comment 11•23 years ago
|
||
Marking verified and browser doesn’t’ not crash when visiting this URL with
build ID 20020124
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•