Closed Bug 661486 Opened 13 years ago Closed 11 years ago

Intermittent test_jQuery.html | application timed out after 330 seconds with no output (sometimes with Assertion failure: type->lazy(), at ../../../js/src/jsinfer.cpp:6341)

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86_64
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: smontagu, Unassigned)

References

Details

(Keywords: intermittent-failure, Whiteboard: [test which aborts the suite]) 

http://tinderbox.mozilla.org/showlog.cgi?log=Mozilla-Aurora/1307000391.1307003062.13838.gz&fulltext=1
Rev3 WINNT 5.1 mozilla-aurora debug test mochitests-2/5 on 2011/06/02 00:39:51
s: talos-r3-xp-047

5585 INFO TEST-PASS | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | fx module: Chain slideDown slideUp - Make sure that opacity is reset (Old: 1 Cur: 1): 1
5586 INFO TEST-PASS | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | fx module: Chain slideDown slideUp - Make sure that height is reset (Old: 0 Cur: 0): 0
5587 INFO TEST-PASS | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | fx module: Chain slideDown slideUp - Make sure that width is reset (Old: 0 Cur: 0): 0
5588 INFO TEST-PASS | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | fx module: Chain slideDown slideUp - Make sure that display is reset (Old: none Cur: none): none
5589 INFO TEST-PASS | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | fx module: Chain slideDown slideUp - Make sure that overflow is reset (Old: visible Cur: visible): visible
WARNING: Subdocument container has no frame: file e:/builds/moz2_slave/aurora-w32-dbg/build/layout/base/nsDocumentViewer.cpp, line 2418
TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | application timed out after 330 seconds with no output

command timed out: 1200 seconds without output, killing pid 4012
program finished with exit code 1
More from the log in comment 1:

9130 INFO TEST-PASS | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | fx module: Chain slideUp slideDown - Make sure that overflow is reset (Old: visible Cur: visible): visible
9131 INFO TEST-PASS | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | fx module: Chain slideToggle in - Make sure that opacity is reset (Old: 1 Cur: 1): 1
9132 INFO TEST-PASS | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | fx module: Chain slideToggle in - Make sure that height is reset (Old: 0 Cur: 0): 0
9133 INFO TEST-PASS | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | fx module: Chain slideToggle in - Make sure that width is reset (Old: 0 Cur: 0): 0
9134 INFO TEST-PASS | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | fx module: Chain slideToggle in - Make sure that display is reset (Old: block Cur: block): block
9135 INFO TEST-PASS | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | fx module: Chain slideToggle in - Make sure that overflow is reset (Old: visible Cur: visible): visible
TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | application timed out after 330 seconds with no output
INFO | automation.py | Application ran for: 0:08:35.469000
INFO | automation.py | Reading PID log: c:\docume~1\cltbld\locals~1\temp\tmpp5dygupidlog
==> process 1616 launched child process 3580
==> process 1616 launched child process 3700
==> process 1616 launched child process 3828
INFO | automation.py | Checking for orphan process with PID: 3580
INFO | automation.py | Checking for orphan process with PID: 3700
INFO | automation.py | Checking for orphan process with PID: 3828
PROCESS-CRASH | /tests/dom/tests/mochitest/ajax/jquery/test_jQuery.html | application crashed (minidump found)
Crash dump filename: c:\docume~1\cltbld\locals~1\temp\tmpbxizsz\minidumps\2767268c-b77e-4f11-8659-5489c4d18299.dmp
Operating system: Windows NT
                  5.1.2600 Service Pack 2
CPU: x86
     GenuineIntel family 6 model 23 stepping 10
     2 CPUs

Crash reason:  EXCEPTION_ACCESS_VIOLATION_WRITE
Crash address: 0x0

Thread 26 (crashed)
 0  crashinjectdll.dll!CrashingThread(void *) [crashinjectdll.cpp:f8fa25d9551c : 13 + 0x0]
    eip = 0x02d51000   esp = 0x082fffb8   ebp = 0x082fffec   ebx = 0x00000000
    esi = 0x57565554   edi = 0x53525150   eax = 0x00000000   ecx = 0x082fffb0
    edx = 0x7c90eb94   efl = 0x00010246
    Found by: given as instruction pointer in context
 1  kernel32.dll + 0xb50a
    eip = 0x7c80b50b   esp = 0x082fffbc   ebp = 0x082fffec
    Found by: call frame info
Keywords: crash
Summary: Timeout in test_jQuery.html after "Chain slideDown slideUp" followed by suite timeout → test_jQuery.html | application timed out after 330 seconds with no output after "Chain slideDown slideUp" or "Chain slideToggle in" followed by crash or suite timeout
Severity: normal → critical
Whiteboard: [orange][test which aborts the suite] → [test which aborts the suite]
We've somewhat morphed this; but guess might as well go with the flow now...
Keywords: crash
OS: Windows XP → Mac OS X
Hardware: x86 → x86_64
Summary: test_jQuery.html | application timed out after 330 seconds with no output after "Chain slideDown slideUp" or "Chain slideToggle in" followed by crash or suite timeout → Intermittent test_jQuery.html | application timed out after 330 seconds with no output
smaug (I picked a random person from the DOM entry on the modules page), can you find an owner for this please.
Flags: needinfo?(bugs)
Summary: Intermittent test_jQuery.html | application timed out after 330 seconds with no output → Intermittent test_jQuery.html | application timed out after 330 seconds with no output (sometimes with Assertion failure: type->lazy(), at ../../../js/src/jsinfer.cpp:6341)
Is this still an issue? The latest tbpl robot comment is from mid May.
Flags: needinfo?(bugs) → needinfo?(emorley)
Happy to close WFM for now :-)
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(emorley)
Resolution: --- → WORKSFORME
and back -> https://tbpl.mozilla.org/php/getParsedLog.php?id=29132508&tree=Mozilla-B2g18
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
This is probably b2g18-only, and since b2g18 is ancient / almost EOL, let's leave this closed for now (still star, but treat like we would for aurora/beta etc, ie: don't reopen the intermittent failure bug) unless it occurs on trunk :-)
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → WORKSFORME
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.