Closed Bug 430615 Opened 12 years ago Closed 12 years ago

ASSERTION: mEditorFlags should not be 0: 'mEditorFlags != 0'

Categories

(Core :: DOM: Editor, defect)

x86
Linux
defect
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: ajschult784, Unassigned)

References

Details

(Keywords: assertion)

Attachments

(1 file)

Attached file stacktrace
nye hits the assertions running mochitests:
###!!! ASSERTION: mEditorFlags should not be 0: 'mEditorFlags != 0', file /build/andrew/moz-debug/mozilla/editor/composer/src/nsEditingSession.cpp, line 1397
###!!! ASSERTION: mStateMaintainer should exist.: 'mStateMaintainer', file /build/andrew/moz-debug/mozilla/editor/composer/src/nsEditingSession.cpp, line 1398

the assertions fire during tests for:
layout/style/test/test_bug319381.html
layout/style/test/test_property_database.html
chrome/toolkit/content/tests/chrome/test_bug331215.xul

Running locally, I only see the assertions with test_bug331215.xul and for that one, it occurs when unloading the previous test for bug 304188.  Stacktrace attached.
nsEditingSession::DetachFromWindow should probably check for mDoneSetup.
This will be fixed by the combined result of the patches for bug 430921 and bug 430624.
Depends on: 430624, 430921
Fixed by checkin for bug 430624.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
FYI, the layout/style/ mochitests no longer hit this, but the assertion still fires during the chrome test (test_bug331215.xul).  (that will still be fixed bug 430921)
Flags: in-testsuite?
You need to log in before you can comment on or make changes to this bug.