Closed Bug 1333955 Opened 7 years ago Closed 7 years ago

Intermittent docshell/test/test_bug402210.html,test_bug404548.html,test_bug475636.html,test_bug509055.html | Assertion count 1 is greater than expected range 0-0 assertions. from "ASSERTION: Destroying a currently-showing document: '!mIsShowing'"

Categories

(Core :: DOM: Navigation, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: intermittent-bug-filer, Unassigned)

References

Details

(Keywords: intermittent-failure)

Summary: Intermittent docshell/test/test_bug402210.html | Assertion count 1 is greater than expected range 0-0 assertions. from "ASSERTION: Destroying a currently-showing document: '!mIsShowing'" → Intermittent docshell/test/test_bug402210.html,test_bug475636.html | Assertion count 1 is greater than expected range 0-0 assertions. from "ASSERTION: Destroying a currently-showing document: '!mIsShowing'"
Summary: Intermittent docshell/test/test_bug402210.html,test_bug475636.html | Assertion count 1 is greater than expected range 0-0 assertions. from "ASSERTION: Destroying a currently-showing document: '!mIsShowing'" → Intermittent docshell/test/test_bug402210.html,test_bug404548.html,test_bug475636.html | Assertion count 1 is greater than expected range 0-0 assertions. from "ASSERTION: Destroying a currently-showing document: '!mIsShowing'"
Summary: Intermittent docshell/test/test_bug402210.html,test_bug404548.html,test_bug475636.html | Assertion count 1 is greater than expected range 0-0 assertions. from "ASSERTION: Destroying a currently-showing document: '!mIsShowing'" → Intermittent docshell/test/test_bug402210.html,test_bug404548.html,test_bug475636.html,test_bug509055.html | Assertion count 1 is greater than expected range 0-0 assertions. from "ASSERTION: Destroying a currently-showing document: '!mIsShowing'"
Priority: -- → P5
See https://wiki.mozilla.org/Bugmasters/Projects/Bug_Handling/Bug_Husbandry#Intermittent_Test_Failure_Cleanup
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.