Closed Bug 469557 Opened 16 years ago Closed 16 years ago

content/html/document/crashtests/353713-1.html | timed out waiting for onload to fire

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Version:
1.9.1 Branch
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: MatsPalmgren_bugz, Unassigned)

References

(
URL
)

Details

This happens occasionally on the Firefox3.1 Linux Tinderboxes.

From today, on moz2-linux-slave10:
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.1/1229269519.1229274379.4613.gz

From today, on moz2-linux-slave13:
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox3.1/1229263331.1229266255.19885.gz
I knew this test was slow when I added it, but I was hoping to get away with it.  Here's what I said when I checked it in on November 29, 2008:

"This test takes about 2 seconds on my machine as it tests mTooDeepWriteRecursion code, making it the slowest crashtest; hopefully this doesn't cause problems."

I guess I lose.  This test should be disabled.  Hopefully I can figure out a way to test bug 353713 (or at least some of the relevant code) without blowing up.
I disabled the tests on 1.9.1 and mozilla-central to fix this intermittent orange.  I filed bug 469626 on creating a better test.
FIXED per last comment
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Component: Content → DOM
QA Contact: content → general
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.