Closed Bug 1272894 Opened 8 years ago Closed 6 years ago

Intermittent test_window_open_close.html | application crashed [None] after Assertion failure: isEmpty() (failing this assertion means this LinkedList's creator is buggy: it should have removed all this list's elements before the list's destruction)

Categories

(Core :: DOM: Core & HTML, defect, P3)

defect

Tracking

()

RESOLVED FIXED
mozilla51
Tracking Status
firefox50 --- fixed
firefox51 --- fixed

People

(Reporter: philor, Assigned: mconley)

References

Details

(Keywords: intermittent-failure)

Depends on: 1277405
Is there some way we can break this into several bugs? There are a lot of different, unrelated failures mixed together here.
Three choices:

* remove the assertion from the summary of this bug, you'll still get every sort of failure in test_window_open_close.html starred as this, and random things like builds that someone didn't bother to notice they still had pinned while they starred something else, and conceivably (though unlikely) a duplicate filed if test_window_open_close.html ever actually manages to crash with a valid minidump and thus a crash signature other than [None], but probably not isEmpty() assertions in other tests

* file a separate bug yourself for every other test which gets misstarred as this

* hire better sheriffs
It looks like something that landed in the past couple of days is causing us to leak the JS runtime at shutdown.
Depends on: 1290567
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
This went away after bug 1290567 landed.
Assignee: nobody → mconley
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla51
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Fascinating that it didn't really go away, but then it really did, but not fascinating enough to have the bug still open.
Status: REOPENED → RESOLVED
Closed: 8 years ago6 years ago
Resolution: --- → FIXED
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.