Closed Bug 606384 Opened 14 years ago Closed 12 years ago

Intermittent timeout in layout/base/crashtests/123049-1.html | timed out waiting for onload to fire

Categories

(Core :: Layout, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: tnikkel, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1287703786.1287704670.24945.gz

REFTEST TEST-START | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/123049-1.html
++DOMWINDOW == 94 (07237E40) [serial = 1012] [outer = 03B496B8]
WARNING: Overflowed nscoord_MAX in conversion to nscoord: file e:\builds\moz2_slave\mozilla-central-win32-debug\build\obj-firefox\dist\include\nsCoord.h, line 359
WARNING: Overflowed nscoord_MAX in conversion to nscoord: file e:\builds\moz2_slave\mozilla-central-win32-debug\build\obj-firefox\dist\include\nsCoord.h, line 359
WARNING: Overflowed nscoord_MAX in conversion to nscoord: file e:\builds\moz2_slave\mozilla-central-win32-debug\build\obj-firefox\dist\include\nsCoord.h, line 359
WARNING: Overflowed nscoord_MAX in conversion to nscoord: file e:\builds\moz2_slave\mozilla-central-win32-debug\build\obj-firefox\dist\include\nsCoord.h, line 359

<snip a bunch of --DOMWINDOW's>

WARNING: NS_ENSURE_TRUE(aListener) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/editor/libeditor/base/nsEditor.cpp, line 1759
REFTEST TEST-UNEXPECTED-FAIL | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/123049-1.html | timed out waiting for onload to fire
Bug 605082, comment 1 has another instance of this.
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
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.