We should investigate what is going on. It seems like it may have started after http://trac.webkit.org/changeset/167325.
Saw regress/script-tests/boolean-test.js.dfg-eager fali in the same non-descriptive manner today, not sure how to tell if it's the same issue. regress/script-tests/boolean-test.js.dfg-eager: test_script_5695: line 2: 77592 Trace/BPT trap: 5 "$@" ../../../.vm/JavaScriptCore.framework/Resources/jsc --useFTLJIT\=false --thresholdForJITAfterWarmUp\=10 --thresholdForJITSoon\=10 --thresholdForOptimizeAfterWarmUp\=20 --thresholdForOptimizeAfterLongWarmUp\=20 --thresholdForOptimizeSoon\=20 --thresholdForFTLOptimizeAfterWarmUp\=20 --thresholdForFTLOptimizeSoon\=20 boolean-test.js regress/script-tests/boolean-test.js.dfg-eager: ERROR: Unexpected exit code: 133 FAIL: regress/script-tests/boolean-test.js.dfg-eager
Created attachment 229649 [details] crash for boolean-test.js.dfg-eager Here is a crash log for boolean-test.js.dfg-eager (no idea if it's the same as the number one).