600417 - Intermittent crash in jsreftest/tests/jsreftest.html?test=ecma_3/Array/15.4.4.3-1.js | application timed out after 330 seconds with no output

Status: RESOLVED WORKSFORME

(Core :: JavaScript Engine, defect)

Description

[(no longer active)]

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1285719381.1285720222.23372.gz
Rev3 MacOSX Leopard 10.5.8 mozilla-central opt test jsreftest on 2010/09/28 17:16:21

REFTEST TEST-START | file:///Users/cltbld/talos-slave/mozilla-central_leopard_test-jsreftest/build/jsreftest/tests/jsreftest.html?test=ecma_3/Array/15.4.4.3-1.js
dyld: lazy symbol binding failed: Symbol not found: _MD5_Update
  Referenced from: /Users/cltbld/talos-slave/mozilla-central_leopard_test-jsreftest/build/Minefield.app/Contents/MacOS/XUL
  Expected in: /Users/cltbld/talos-slave/mozilla-central_leopard_test-jsreftest/build/Minefield.app/Contents/MacOS/libssl3.dylib

dyld: Symbol not found: _MD5_Update
  Referenced from: /Users/cltbld/talos-slave/mozilla-central_leopard_test-jsreftest/build/Minefield.app/Contents/MacOS/XUL
  Expected in: /Users/cltbld/talos-slave/mozilla-central_leopard_test-jsreftest/build/Minefield.app/Contents/MacOS/libssl3.dylib

TEST-UNEXPECTED-FAIL | file:///Users/cltbld/talos-slave/mozilla-central_leopard_test-jsreftest/build/jsreftest/tests/jsreftest.html?test=ecma_3/Array/15.4.4.3-1.js | application timed out after 330 seconds with no output
Can't trigger Breakpad, just killing process
INFO | automation.py | Application ran for: 0:08:06.441934
INFO | automation.py | Reading PID log: /var/folders/Xr/Xr--yJnSEY0U11ET5NZuMU+++TM/-Tmp-/tmpRlZo_8pidlog
PROCESS-CRASH | file:///Users/cltbld/talos-slave/mozilla-central_leopard_test-jsreftest/build/jsreftest/tests/jsreftest.html?test=ecma_3/Array/15.4.4.3-1.js | application crashed (minidump found)

Comment 1

[Ed Morley [:emorley]]

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