[FIX]"ASSERTION: Should be in an update while destroying frames" with document.write into iframe

RESOLVED FIXED

Status

()

Core
Layout
RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: Jesse Ruderman, Assigned: bz)

Tracking

({assertion, testcase})

Trunk
assertion, testcase
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

10 years ago
Loading the testcase triggers:

###!!! ASSERTION: Should be in an update while destroying frames: 'mUpdateCount != 0', file /Users/jruderman/trunk/mozilla/layout/base/nsCSSFrameConstructor.cpp, line 9453

Reduced from layout/reftests/bugs/388980-1-ref.html, which also triggers the assertion, so in-testsuite+.
Flags: in-testsuite+
(Reporter)

Comment 1

10 years ago
Created attachment 301051 [details]
testcase
(Reporter)

Updated

10 years ago
Blocks: 385276
Created attachment 301177 [details] [diff] [review]
I had this hanging out in one of my trees....
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
Attachment #301177 - Flags: superreview?(jst)
Attachment #301177 - Flags: review?(jst)
OS: Mac OS X → All
Hardware: PC → All
Summary: "ASSERTION: Should be in an update while destroying frames" with document.write into iframe → [FIX]"ASSERTION: Should be in an update while destroying frames" with document.write into iframe

Updated

10 years ago
Attachment #301177 - Flags: superreview?(jst)
Attachment #301177 - Flags: superreview+
Attachment #301177 - Flags: review?(jst)
Attachment #301177 - Flags: review+
Comment on attachment 301177 [details] [diff] [review]
I had this hanging out in one of my trees....

Requesting approval.  This should be fairly safe, and fixes an assertion that Jesse ran into...
Attachment #301177 - Flags: approval1.9?

Updated

10 years ago
Attachment #301177 - Flags: approval1.9? → approval1.9+
Fixed.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.