Closed Bug 605392 Opened 14 years ago Closed 12 years ago

[Windows] Intermittent failure in 143862-1b.html | timed out waiting for onload to fire

Categories

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

x86
Windows Server 2003
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: sicking, Unassigned)

References

Details

(Keywords: intermittent-failure)

http://tinderbox.mozilla.org/showlog.cgi?tree=Firefox&errorparser=unittest&logfile=1287469740.1287471038.9352.gz&buildtime=1287469740&buildname=WINNT%205.2%20mozilla-central%20debug%20test%20crashtest&fulltext=1

The following part seems relevant:

WARNING: NS_ENSURE_TRUE(selcon) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/editor/libeditor/base/nsEditor.cpp, line 587
WARNING: NS_ENSURE_TRUE(ps) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/editor/libeditor/html/nsHTMLEditor.cpp, line 3599
++DOMWINDOW == 49 (03FB2BD8) [serial = 1019] [outer = 03B27750]
REFTEST TEST-START | file:///e:/builds/moz2_slave/mozilla-central-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/143862-1b.html
++DOMWINDOW == 50 (04D8E3B0) [serial = 1020] [outer = 03B27750]
pldhash: for the table at address 096D6380, the given entrySize of 48 probably favors chaining over double hashing.
++DOCSHELL 096D6318 == 5
++DOMWINDOW == 51 (08A8B8E8) [serial = 1021] [outer = 00000000]
WARNING: NS_ENSURE_TRUE(shell) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/docshell/base/nsDocShell.cpp, line 10601
WARNING: NS_ENSURE_TRUE(sf) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/docshell/base/nsDocShell.cpp, line 4914
WARNING: NS_ENSURE_TRUE(shell) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/docshell/base/nsDocShell.cpp, line 10601
WARNING: NS_ENSURE_TRUE(sf) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/docshell/base/nsDocShell.cpp, line 4914
++DOMWINDOW == 52 (0921DE98) [serial = 1022] [outer = 08A8B8B0]
143862-1-inner.html: A
143862-1-inner.html: B
++DOMWINDOW == 53 (057BBFB0) [serial = 1023] [outer = 08A8B8B0]
WARNING: NS_ENSURE_TRUE(selcon) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/editor/libeditor/base/nsEditor.cpp, line 587
WARNING: NS_ENSURE_TRUE(ps) failed: file e:/builds/moz2_slave/mozilla-central-win32-debug/build/editor/libeditor/html/nsHTMLEditor.cpp, line 3599
143862-1-inner.html: C
143862-1-inner.html: D
WARNING: ContentViewer exists outside gHistoryMaxViewer range: '!viewer', file e:/builds/moz2_slave/mozilla-central-win32-debug/build/docshell/shistory/src/nsSHistory.cpp, line 850

...

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/143862-1b.html | timed out waiting for onload to fire
Blocks: 438871
Whiteboard: [orange]
Blocks: 540980
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1289034214.1289036291.16147.gz&fulltext=1
WINNT 5.2 comm-central-trunk debug test crashtest on 2010/11/06 02:03:34
{
TEST-UNEXPECTED-FAIL | file:///e:/builds/slave/comm-central-trunk-win32-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/143862-1b.html | application timed out after 330 seconds with no output
buildbot.slave.commands.TimeoutError: command timed out: 1200 seconds without output
}
OS: Mac OS X → Windows Server 2003
Summary: Intermittent failure in 143862-1b.html | timed out waiting for onload to fire → [Windows] Intermittent failure in 143862-1b.html | timed out waiting for onload to fire
Depends on: 633718
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]
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.