Closed
Bug 429881
Opened 16 years ago
Closed 16 years ago
"ASSERTION: Dead placeholder in placeholder map" with -moz-column, r/a/f positioning
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jruderman, Assigned: jruderman)
References
Details
(Keywords: assertion, crash, testcase, Whiteboard: [sg:critical?])
Attachments
(1 file)
(deleted),
text/html
|
Details |
###!!! ASSERTION: Placeholder relationship should have been torn down; see comments in nsPlaceholderFrame.h: '!shell->FrameManager()->GetPlaceholderFrameFor(mOutOfFlowFrame)', file /Users/jruderman/trunk/mozilla/layout/generic/nsPlaceholderFrame.cpp, line 132 ###!!! ASSERTION: Dead placeholder in placeholder map: 'entry->placeholderFrame->GetOutOfFlowFrame() != (void*)0xdddddddd', file /Users/jruderman/trunk/mozilla/layout/base/nsFrameManager.cpp, line 136 ###!!! ASSERTION: no placeholder frame: 'nsnull != placeholderFrame', file /Users/jruderman/trunk/mozilla/layout/generic/nsHTMLReflowState.cpp, line 1104 Crash [@ nsHTMLReflowState::GetNearestContainingBlock] or [@ nsCSSFrameConstructor::RemoveFixedItems]
Assignee | ||
Comment 1•16 years ago
|
||
See also bug 428113, which triggers some of the same assertions with a very different testcase.
Comment 2•16 years ago
|
||
this still crashes on Windows and Mac with the testcase also after the landing from the Patch in Bug 398332
OS: Mac OS X → All
Hardware: PC → All
Comment 3•16 years ago
|
||
Tomcat, could you pls provide the stack trace for each OS? It'll be interesting to see if it crashes at which one of [@ nsHTMLReflowState::GetNearestContainingBlock] or [@ nsCSSFrameConstructor::RemoveFixedItems].
Assignee | ||
Comment 4•16 years ago
|
||
While this doesn't crash, an assertion about seeing 0xdddddddd is scary enough to warrant [sg:critical?].
Whiteboard: [sg:critical?]
Assignee | ||
Comment 5•16 years ago
|
||
WFM on mozilla-central.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Comment 6•16 years ago
|
||
It still occurs in 1.9.1 and 1.9.0 though. It was fixed on trunk in the range 2008-12-07-02 -- 2008-12-08-02: http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=2008-12-07+00%3A01%3A00&enddate=2008-12-08+00%3A03%3A00 Applying the patch in bug 411835 fixes it on 1.9.1
Comment 7•10 years ago
|
||
Landed a crashtest: https://hg.mozilla.org/integration/mozilla-inbound/rev/b35d611a0dce
Group: core-security
Flags: in-testsuite? → in-testsuite+
Comment 8•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/b35d611a0dce
Assignee: nobody → jruderman
You need to log in
before you can comment on or make changes to this bug.
Description
•