Closed
Bug 31312
Opened 25 years ago
Closed 24 years ago
browse crashed if I open the URL specified
Categories
(Core :: DOM: HTML Parser, defect, P3)
Tracking
()
M15
People
(Reporter: Rui.Monteiro, Assigned: buster)
References
()
Details
(Keywords: crash)
Attachments
(2 files)
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; N; Linux 2.2.12-20 i686; en-US; m14) BuildID: 2000030913 Every browse windows crash when these pages are loaded. The problem should be somewhere between ActiveX, CSS and Javascript support ;-). I receive no error message from the console so I'm unable to be more specific :-(. This URL is weird. Sometimes Netscape 4.7 freezes while loading the same page so I suspect is Javascript that's causing the problem. Reproducible: Always Steps to Reproduce: 1.open the URL: http://www.diariodigital.pt 2. 3. Actual Results: No matter how many windows of the mozilla I have opened it simply closes all of them with no error message whatsoever. Expected Results: It should open a multi framed window with a graphic animation widget in Javascript runing from left to right of the central frame. I have no additional information. Keep the good work :-)
Comment 1•25 years ago
|
||
I'm crashing as well on Linux build 2000.03.09.13, in the middle frame. I edited out all the JS and tables, and I'm still crashing. Attaching the pared-down page. It's still very long. Reassign to Parser.
Assignee: rogerl → rickg
Component: Javascript Engine → Parser
QA Contact: rginda → janc
Updated•25 years ago
|
Comment 2•25 years ago
|
||
Waqar: I can't reproduce this on NT. Can you see this on linux?
Assignee: rickg → waqar
I think this a stack overflow problem, I have narrowed down the test case further.
Status: NEW → ASSIGNED
Target Milestone: M15
Steve here is the dupe of one of your bugs. This the nested bold tags that is hosing the stack.
Assignee: waqar → buster
Status: ASSIGNED → NEW
*** This bug has been marked as a duplicate of 32201 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•