If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

"nsnull != nextFrame" assertion spewage

VERIFIED FIXED

Status

()

Core
Layout
P3
normal
VERIFIED FIXED
18 years ago
17 years ago

People

(Reporter: tor, Assigned: troy)

Tracking

Trunk
Sun
Solaris
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

18 years ago
The new design at www.intel.com appears to be causing problems for mozilla.
On a 5/2 cvs pull (post tree closing), I get pages of errors of this form:

###!!! ASSERTION: next frame in reflow command is null: 'nsnull != nextFrame',
file /cs/src/mozilla/mozilla/layout/html/base/src/nsAbsoluteContainingBlock.cpp,
line 337
###!!! Break: at file
/cs/src/mozilla/mozilla/layout/html/base/src/nsAbsoluteContainingBlock.cpp, line
337
###!!! ASSERTION: null ptr: 'nsnull != aFrame', file
/cs/src/mozilla/mozilla/layout/base/src/nsFrameList.cpp, line 306
###!!! Break: at file /cs/src/mozilla/mozilla/layout/base/src/nsFrameList.cpp,
line 306
(Reporter)

Comment 1

18 years ago
Meant to say a 5/3 cvs pull (on solaris/native).
(Assignee)

Comment 2

18 years ago
Fixed by Chris's checkin to nsAbsoluteContainingBlock
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED

Comment 3

17 years ago
Marking verified per last comments.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.