Closed
Bug 47200
Opened 24 years ago
Closed 24 years ago
www.crn.com crash
Categories
(Core :: Layout, defect, P2)
Tracking
()
M18
People
(Reporter: granrosebugs, Assigned: attinasi)
References
()
Details
(Keywords: crash, helpwanted, Whiteboard: nsbeta3+)
Reported on n.p.m.general: Noticed this in the past few builds, ever since CRN updated their website: <http://www.crn.com/Sections/BreakingNews/default.asp> Click on any news link, instant crash. What is causing this? ----------------------- Scott I. Remick scott@computeralt.com Network and Information (802)388-7545 ext. 236 Systems Manager FAX:(802)388-3697 Computer Alternatives, Inc. http://www.computeralt.com ============================================== Verified this crash exists on both the M17 branch and on the trunk. Something very weird going on with their site when mousing over links. But even so, we shouldn't crash on it. Filed a talkback report, will attach when available.
Reporter | ||
Updated•24 years ago
|
Reporter | ||
Comment 1•24 years ago
|
||
Steps to reproduce: 1 - go to http://www.crn.com/sections/BreakingNews/default.asp 2 - click on any link in the middle news section. 3 - crash. URL at the top of the news section right now is http://www.crn.com/sections/BreakingNews/dailyarchives.asp?ArticleID=18911
Reporter | ||
Comment 2•24 years ago
|
||
Talkback stack trace is rather large, so I won't paste it here, but it's at http://climate.mcom.com/reports/incidenttemplate.CFM?reportID=1129&style=0&tc=19&cp=2&bbid=15123584 and here's the first few lines: 0x00000004 nsFrameList::DestroyFrames [d:\builds\seamonkey\mozilla\layout\base\src\nsFrameList.cpp, line 35] nsAbsoluteContainingBlock::DestroyFrames [d:\builds\seamonkey\mozilla\layout\html\base\src\nsAbsoluteContainingBlock.cpp, line 365] nsPositionedInlineFrame::Destroy [d:\builds\seamonkey\mozilla\layout\html\base\src\nsInlineFrame.cpp, line 945] nsFrameList::DestroyFrames [d:\builds\seamonkey\mozilla\layout\base\src\nsFrameList.cpp, line 36] nsContainerFrame::Destroy [d:\builds\seamonkey\mozilla\layout\html\base\src\nsContainerFrame.cpp, line 98] nsLineBox::DeleteLineList [d:\builds\seamonkey\mozilla\layout\html\base\src\nsLineBox.cpp, line 252] nsBlockFrame::Destroy [d:\builds\seamonkey\mozilla\layout\html\base\src\nsBlockFrame.cpp, line 1222] nsFrameList::DestroyFrames [d:\builds\seamonkey\mozilla\layout\base\src\nsFrameList.cpp, line 36] nsContainerFrame::Destroy [d:\builds\seamonkey\mozilla\layout\html\base\src\nsContainerFrame.cpp, line 98] nsFrameList::DestroyFrames [d:\builds\seamonkey\mozilla\layout\base\src\nsFrameList.cpp, line 36] nsContainerFrame::Destroy [d:\builds\seamonkey\mozilla\layout\html\base\src\nsContainerFrame.cpp, line 98] nsFrameList::DestroyFrames [d:\builds\seamonkey\mozilla\layout\base\src\nsFrameList.cpp, line 36] nsContainerFrame::Destroy [d:\builds\seamonkey\mozilla\layout\html\base\src\nsContainerFrame.cpp, line 98] nsFrameList::DestroyFrames [d:\builds\seamonkey\mozilla\layout\base\src\nsFrameList.cpp, line 36]
Comment 3•24 years ago
|
||
over to layout.
Assignee: asa → clayton
Component: Browser-General → Layout
QA Contact: doronr → petersen
Assignee | ||
Comment 7•24 years ago
|
||
Scroll down and you see that the layout is all mesed up too... I'll investigate further, especially the ReflowState assertions (18 of them) when just loading the page.
Status: NEW → ASSIGNED
Assignee | ||
Comment 8•24 years ago
|
||
I could really really use some help narrowing this down. The page is huge and very complicated. I have narrowed down the style rules to one rule that will make this crash or not: #AIRboxwrapper {visibility: visible; padding: 0px; border-width: 0px; border-style: none; margin: 0px; position: absolute; top: -405px; left: -55px; width: 155px;} I have removed all other style rules and the LINK'd stylesheet and it still crashes. Also, I have removed large parts of the page (from the BODY to the table with the MAP) and it still crashes. There is lots of embedded script that makes it harder still to narrow down - please help if you can. Approving for beta3+ since it is a crash in layout, apparently related to absolute positioning (though the exact nature of the crash is not yet known). Note that without being able to narrow this down it will probably nt get fixed, so your help is very much needed!
Assignee | ||
Comment 9•24 years ago
|
||
I don't know how relevant this is, but the attachment http://bugzilla.mozilla.org/showattachment.cgi?attach_id=12899 results in the same assertion, and it crashes on unload the same way too...
Assignee | ||
Comment 10•24 years ago
|
||
After three days of debugging I found out it's a dup of another bug, marked beta3+ also, in Buster's queue (bug 42372). This is a problem of frame parentage of relative and absolutely positioned elements... *** This bug has been marked as a duplicate of 42372 ***
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•