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

Failure in layout/reftests/editor/dynamic-type-1.html (with "load failed: null")

RESOLVED WORKSFORME

Status

()

Core
XPCOM
RESOLVED WORKSFORME
6 years ago
5 years ago

People

(Reporter: roc, Unassigned)

Tracking

({intermittent-failure})

Firefox Tracking Flags

(Not tracked)

Details

I'm not sure what to make of this.

http://tinderbox.mozilla.org/showlog.cgi?log=Cedar/1306727771.1306729518.27995.gz&fulltext=1#err0

The salient part:

REFTEST TEST-START | file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/reftests/editor/dynamic-type-1.html
++DOMWINDOW == 76 (0x10aa37db8) [serial = 8298] [outer = 0x1085c4820]
WARNING: An event was posted to a thread that will never run it (rejected): file /builds/slave/ced-osx64-dbg/build/xpcom/threads/nsThread.cpp, line 375
WARNING: leaking reference to nsTimerImpl: file /builds/slave/ced-osx64-dbg/build/xpcom/threads/nsTimerImpl.cpp, line 494
--DOMWINDOW == 75 (0x12ab599a8) [serial = 8293] [outer = 0x1085c4820] [url = file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/reftests/editor/newline-4.html]
--DOMWINDOW == 74 (0x125547d88) [serial = 8292] [outer = 0x1085c4820] [url = data:text/html,%3C%21%2D%2DCLEAR%2D%2D%3E]
--DOMWINDOW == 73 (0x1255ddfb8) [serial = 8291] [outer = 0x1085c4820] [url = file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/reftests/editor/newline-3.html]
--DOMWINDOW == 72 (0x133adca58) [serial = 8290] [outer = 0x1085c4820] [url = data:text/html,%3C%21%2D%2DCLEAR%2D%2D%3E]
--DOMWINDOW == 71 (0x10bdbf0e8) [serial = 8289] [outer = 0x1085c4820] [url = file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/reftests/editor/newline-2.html]
--DOMWINDOW == 70 (0x10b0b3b98) [serial = 8288] [outer = 0x1085c4820] [url = data:text/html,%3C%21%2D%2DCLEAR%2D%2D%3E]
--DOMWINDOW == 69 (0x10b0adaf8) [serial = 8287] [outer = 0x1085c4820] [url = file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/reftests/editor/newline-ref.html]
--DOMWINDOW == 68 (0x124579fd8) [serial = 8286] [outer = 0x1085c4820] [url = file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/reftests/editor/newline-1.html]
REFTEST TEST-UNEXPECTED-FAIL | file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/reftests/editor/dynamic-type-1.html | load failed: null
REFTEST INFO | Saved log: START file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/reftests/editor/dynamic-type-1.html
REFTEST INFO | Loading a blank page
WARNING: 1 sort operation has occurred for the SQL statement '0x133295158'.  See https://developer.mozilla.org/En/Storage/Warnings details.: file /builds/slave/ced-osx64-dbg/build/storage/src/mozStoragePrivateHelpers.cpp, line 144
pldhash: for the table at address 0x10b0e42d0, the given entrySize of 168 definitely favors chaining over double hashing.
WARNING: 1 sort operation has occurred for the SQL statement '0x10aa39998'.  See https://developer.mozilla.org/En/Storage/Warnings details.: file /builds/slave/ced-osx64-dbg/build/storage/src/mozStoragePrivateHelpers.cpp, line 144
++DOMWINDOW == 69 (0x125505ff8) [serial = 8299] [outer = 0x1085c4820]
REFTEST TEST-START | file:///Users/cltbld/talos-slave/test/build/reftest/tests/layout/reftests/editor/dynamic-type-2.html

It looks like the file just didn't load. But the test file is very simple. I suspect this is not editor-related but some kind of intermittent failure in page loading itself.

The warning "An event was posted to a thread that will never run it (rejected)" looks interesting. It means an event was posted to a thread that has already ended its event loop as part of Shutdown. Of course we have no idea what thread or event that might be, but if we did then maybe we could solve this.
Blocks: 438871
Hmm, that line about leaking a timer was interesting.  By some code inspection, it seems like the timer thread has fired a timer event to a thread which is shutting down.  I don't know if that is something which is expected...
Component: Layout → XPCOM
QA Contact: layout → xpcom
Not sure about "expected", but it could easily happen, no?  As long as the thread that's shutting down didn't cancel the timer and all.
Comment hidden (Treeherder Robot)
Comment hidden (Treeherder Robot)

Comment 5

5 years ago
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WORKSFORME
(Assignee)

Updated

5 years ago
Keywords: intermittent-failure
(Assignee)

Updated

5 years ago
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.