http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1290310587.1290310918.22708.gz&fulltext=1 Linux comm-central-trunk debug test crashtest on 2010/11/20 19:36:27 s: cb-seamonkey-linux-02 { REFTEST TEST-START | file:///builds/slave/comm-central-trunk-linux-debug-unittest-crashtest/build/reftest/tests/layout/svg/crashtests/587336-1.html ... TEST-UNEXPECTED-FAIL | file:///builds/slave/comm-central-trunk-linux-debug-unittest-crashtest/build/reftest/tests/layout/svg/crashtests/587336-1.html | Exited with code -11 during test run INFO | automation.py | Application ran for: 0:04:31.276443 ... }

I'm not sure what happened here, from the log -- was this a crash, or a hang-that-was-interrupted, or what? (There's no stack, which I thought we normally printed out in those cases...)

(In reply to comment #1) > I'm not sure what happened here, from the log -- was this a crash, or a > hang-that-was-interrupted, or what? (There's no stack, which I thought we > normally printed out in those cases...) Same thought here, but I have no clue. ***** Hum, http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1286818366.1286818589.6026.gz Linux comm-central-trunk debug test crashtest on 2010/10/11 10:32:46 already had { REFTEST TEST-START | file:///builds/slave/comm-central-trunk-linux-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/457362-1.xhtml TEST-UNEXPECTED-FAIL | file:///builds/slave/comm-central-trunk-linux-debug-unittest-crashtest/build/reftest/tests/layout/base/crashtests/457362-1.xhtml | Exited with code -11 during test run INFO | automation.py | Application ran for: 0:02:56.906188 } http://mxr.mozilla.org/mozilla-central/source/layout/base/crashtests/457362-1.xhtml http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1289371557.1289371777.5489.gz Linux comm-central-trunk debug test crashtest on 2010/11/09 22:45:57 moz:43781a14501d was the last build failing in 457362-1.xhtml http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1289382329.1289382753.22898.gz Linux comm-central-trunk debug test crashtest on 2010/11/10 01:45:29 moz:f174fb3f8e59 is the first build to fail in 587336-1.html New test timeframe: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=43781a14501d&tochange=f174fb3f8e59 --> which is when bug 587336 added this test.

Wild guess: too-much-recursion crash and breakpad couldn't deal with it.

http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1296017209.1296017521.7583.gz&fulltext=1 Linux comm-central-trunk debug test crashtest on 2011/01/25 20:46:49 { REFTEST TEST-START | file:///builds/slave/test/build/reftest/tests/layout/generic/crashtests/505912-1.html ++DOMWINDOW == 40 (0xaab96a04) [serial = 2663] [outer = 0x8f2fb48] For application/x-test found plugin libnptest.so ### XPCOM_MEM_BLOAT_LOG defined -- logging bloat/leaks to /tmp/tmpPENenv/runreftest_leaks_plugin_pid18641.log ... REFTEST TEST-PASS | file:///builds/slave/test/build/reftest/tests/layout/generic/crashtests/505912-1.html | (LOAD ONLY) ... REFTEST TEST-START | file:///builds/slave/test/build/reftest/tests/layout/svg/crashtests/587336-1.html ++DOMWINDOW == 128 (0xaf920e7c) [serial = 3202] [outer = 0x8f2fb48] WARNING: shutting down early because of crash!: file /builds/slave/comm-cen-trunk-lnx-dbg/build/mozilla/dom/plugins/PluginModuleChild.cpp, line 600 WARNING: plugin process _exit()ing: file /builds/slave/comm-cen-trunk-lnx-dbg/build/mozilla/dom/plugins/PluginModuleChild.cpp, line 592 TEST-UNEXPECTED-FAIL | file:///builds/slave/test/build/reftest/tests/layout/svg/crashtests/587336-1.html | Exited with code -11 during test run ... ==> process 18585 launched child process 18641 INFO | automation.py | Checking for orphan process with PID: 18641 TEST-UNEXPECTED-FAIL | plugin process 18641 | automationutils.processLeakLog() | missing output line for total leaks! } libnptest.so is crashing. http://mxr.mozilla.org/mozilla-central/source/dom/plugins/PluginModuleChild.cpp 596 void 597 PluginModuleChild::ActorDestroy(ActorDestroyReason why) 598 { 599 if (AbnormalShutdown == why) { 600 NS_WARNING("shutting down early because of crash!"); 601 QuickExit(); 602 } *** "blocking2.0=?": Bug 587336 was blocking2.0+. It should at least be investigated whether the issue is in Core or the/a test or SeaMonkey... As this failure is permanent, it should be easy to record and analyze this crash...

(In reply to comment #4) > It should at least be investigated whether the issue is in Core or the/a test > or SeaMonkey... Or could it be some "CentOS vs Fedora" dependency?

Saw this over the weekend in a valgrind unit test run on a 64 bit Centos 5 box REFTEST TEST-START | file:///work/mozilla/builds/2.0.0/mozilla/layout/svg/crashtests/587336-1.html ++DOMWINDOW == 11 (0x10998bd8) [serial = 3203] [outer = 0x108753d0] ==14399== Stack overflow in thread 1: can't grow stack to 0x7fe601fe8 ==14399== Can't extend stack to 0x7fe601400 during signal delivery for thread 1: ==14399== no stack segment ==14399== ==14399== Process terminating with default action of signal 11 (SIGSEGV) ==14399== Access not within mapped region at address 0x7FE601400 ==14399== at 0x887122D: PL_HashTableLookup (plhash.c:360) ==14399== If you believe this happened as a result of a stack ==14399== overflow in your program's main thread (unlikely but ==14399== possible), you can try to increase the size of the ==14399== main thread stack using the --main-stacksize= flag. ==14399== The main thread stack size used in this run was 10485760. ==14399==

bc, did valgrind give you a stack trace for the stack overflow crash?

no, just what i pasted in comment 6.

Bug still there: (SM 2.9a1) http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1326817147.1326817854.19149.gz Linux comm-central-trunk debug test crashtest on 2012/01/17 08:19:07 { ... REFTEST TEST-PASS | file:///builds/slave/test/build/reftest/tests/layout/svg/crashtests/566216-1.svg | (LOAD ONLY) REFTEST INFO | Loading a blank page ++DOMWINDOW == 22 (0xaa25b70) [serial = 3547] [outer = 0x9982e90] REFTEST TEST-START | file:///builds/slave/test/build/reftest/tests/layout/svg/crashtests/587336-1.html | 1554 / 2001 (77%) ++DOMWINDOW == 23 (0xa257490) [serial = 3548] [outer = 0x9982e90] WARNING: shutting down early because of crash!: file /builds/slave/comm-cen-trunk-lnx-dbg/build/mozilla/dom/plugins/ipc/PluginModuleChild.cpp, line 743 WARNING: plugin process _exit()ing: file /builds/slave/comm-cen-trunk-lnx-dbg/build/mozilla/dom/plugins/ipc/PluginModuleChild.cpp, line 708 TEST-UNEXPECTED-FAIL | file:///builds/slave/test/build/reftest/tests/layout/svg/crashtests/587336-1.html | Exited with code -11 during test run INFO | automation.py | Application ran for: 0:09:46.729953 INFO | automation.py | Reading PID log: /tmp/tmpamfnG6pidlog ==> process 21111 launched child process 21763 INFO | automation.py | Checking for orphan process with PID: 21763 TEST-UNEXPECTED-FAIL | plugin process 21763 | automationutils.processLeakLog() | missing output line for total leaks! TEST-UNEXPECTED-FAIL | automationutils.processLeakLog() | missing output line for total leaks! REFTEST INFO | runreftest.py | Running tests: end. program finished with exit code 245 elapsedTime=595.758842 } ***** If cause can't be found+fix, then we need to disable this test on SeaMonkey Linux (tinderbox)!