ASSERTION: illegal next frame in incremental reflow.

RESOLVED WORKSFORME

Status

()

Core
Layout: Tables
RESOLVED WORKSFORME
12 years ago
12 years ago

People

(Reporter: Martijn Wargers (zombie), Unassigned)

Tracking

({assertion, testcase})

Trunk
x86
Windows XP
assertion, testcase
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

12 years ago
See upcoming testcase, which gives this assertion in my debug build.
(Reporter)

Comment 1

12 years ago
Created attachment 227092 [details]
testcase

The testcase consists of this:
<table>
<html style="">
<caption>
<caption>
<div>
<table>
<q>
<span>
<div>
<table>
(Reporter)

Comment 2

12 years ago
Created attachment 227093 [details]
Backtrace from debug build

#1  0x005424b5 in Break (
    aMsg=0x22d348 "###!!! ASSERTION: illegal next frame in incremental reflow.:
'PR_FALSE', file c:/mozilla/mozilla/layout/tables/nsTableOuterFrame.cpp, line 13
73") at c:/mozilla/mozilla/xpcom/base/nsDebugImpl.cpp:433
#2  0x00542237 in NS_DebugBreak_P (aSeverity=1,
    aStr=0x5d6dfec "illegal next frame in incremental reflow.",
    aExpr=0x5d6dc74 "PR_FALSE",
    aFile=0x5d6dc04 "c:/mozilla/mozilla/layout/tables/nsTableOuterFrame.cpp",
    aLine=1373) at c:/mozilla/mozilla/xpcom/base/nsDebugImpl.cpp:350
#3  0x0583fb59 in nsTableOuterFrame::IR_TargetIsChild (this=0x10747408,
    aPresContext=0x1073dc98, aDesiredSize=@0x22dd2c, aReflowState=@0x22db08,
    aStatus=@0x22db04, aNextFrame=0x10747764)
    at c:/mozilla/mozilla/layout/tables/nsTableOuterFrame.cpp:1373
#4  0x0583f9f2 in nsTableOuterFrame::IncrementalReflow (this=0x10747408,
    aPresContext=0x1073dc98, aDesiredSize=@0x22dd2c, aReflowState=@0x22db08,
    aStatus=@0x22db04)
    at c:/mozilla/mozilla/layout/tables/nsTableOuterFrame.cpp:1339
etc.

Comment 3

12 years ago
I've hit this assertion too.
(Reporter)

Comment 4

12 years ago
This is worksforme with current debug trunk build.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.