Closed Bug 121591 Opened 24 years ago Closed 23 years ago

This URL crashes Mozilla (nightly build as of 2002-Jan-24

Categories

(Core :: Layout, defect, P1)

defect

Tracking

()

VERIFIED WORKSFORME
Future

People

(Reporter: lars, Assigned: attinasi)

References

()

Details

(Keywords: crash, regression, testcase)

Attachments

(4 files)

Mozilla crashes immediately after selecting the above URL (and before anything is displayed). If the above URL doesn't work (it looks as if there may be some kind of per-session information embedded in it), try the following: http://jobs.boston.com/texis/js?view=2&lookid=boston&q=unix+analyst&qMatch=all&qField=Title&qInd=&qLoc=ma&qMiles=&qcompid=&qSort=date&Search.x=64&Search.y=14 That ought to bring up a single result, which is the job listing that is crashing Mozilla on my system.
Reporter: Please always use severity level "critical" for crashes.
True with w2k 2002012304. Reporter change OS => ALL. Talk back does not seem to work Will post talkback ID when I'll get the ID.
Build ID: 2002 01 23 04. Windows 2000. I can reproduce the crash. An incident is queued, but "talkback.netscape.com" seems to be down...
Talkback ID is TB2053931Y.
Confirming on Linux, marking NEW, OS=ALL as per comments, severity critical. From gdb backtrace it looks like XPCOM. Reassigning. Backtrace follows.
Severity: major → critical
Status: UNCONFIRMED → NEW
Component: Browser-General → XPCOM
Ever confirmed: true
OS: Linux → All
The Incident ID of my crash: TB2053407Z
Keywords: crash
Attached file Stack trace for MacOSX
Also crashes on macosX. Platform should be => ALL.
-> Default owner (also crashing on win2k) Could be layout related because of the nsCSSFrameConstructor stuff and this assertitions before the crash: ###!!! ASSERTION: frame was not removed from primary frame map before destructio n or was readded to map after being removed: '!PL_DHASH_ENTRY_IS_BUSY(entry) || entry->frame != aFrame', file D:\moz_source\normal\mozilla\layout\html\base\src\ nsFrameManager.cpp, line 1003 CC dbaron (is this bug layout related ?)
Assignee: asa → dougt
QA Contact: doronr → scc
Matti can you cahnge Platform to all ?
I would first have the client of xpcom take a look at this... html frames?
Assignee: dougt → eric
Component: XPCOM → HTMLFrames
QA Contact: scc → amar
Hardware: PC → All
->Layout
Assignee: eric → attinasi
Component: HTMLFrames → Layout
QA Contact: amar → petersen
Target Milestone: --- → mozilla0.9.9
Marking nsbeta1+
Keywords: nsbeta1+
Changing to P1.
Priority: -- → P1
The basice structure of this test case is the following: HTML-- > TABLE --> FONT --> HTML --> TABLE --> TABLE --> FORM
Adding testcase
Keywords: testcase
Looking at this, I do not think it is all that critical. Sure, it crashes, but the markup is very bad and very specific - I do not think it is the most serious crasher we have. I wanted to look at it because I have seen that assertion more than I'd like - I'll downgrade to a P2 for now only because I have other more common crashers to look at, and hopefully I can get back to this one in the current milestone.
Status: NEW → ASSIGNED
Keywords: nsbeta1+nsbeta1
Priority: P1 → P2
BTW: this is a regerssion, Netscape 6.2.1 works fine :)
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Keywords: regression
Resolution: --- → FIXED
How did this get marked fixed? Sheesh, reopening...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → ASSIGNED
Marking nsbeta1- based on Marc's comment "markup is very bad and very specific"
Keywords: nsbeta1nsbeta1-
Moving out to 1.0.1 for nsbeta1-
Target Milestone: mozilla0.9.9 → mozilla1.0.1
Moving Mozilla 1.01 bugs to 'future' milestone with priority P1 I will be pulling bugs from 'future' milestones when scheduling later work.
Priority: P2 → P1
Target Milestone: mozilla1.0.1 → Future
I'm not crashing on a win2k debug build. wfm.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago23 years ago
Resolution: --- → WORKSFORME
Verified WFM in the April 23rd build OS X(2002-04-23-08) and Windows ME (2002-04-23-06).
Status: RESOLVED → VERIFIED
Flags: in-testsuite+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: