The following layout tests fail (or are flaky) because they run out of memory: js/slow-stress/Int32Array-alloc-huge-long-lived.html js/slow-stress/Int32Array-alloc-large-long-lived.html Example output: --- /cygdrive/c/Projects/WebKit/OpenSource/WebKitBuild/Release/bin32/layout-test-results/js/slow-stress/Int32Array-alloc-huge-long-lived-expected.txt +++ /cygdrive/c/Projects/WebKit/OpenSource/WebKitBuild/Release/bin32/layout-test-results/js/slow-stress/Int32Array-alloc-huge-long-lived-actual.txt @@ -1,10 +1,11 @@ +CONSOLE MESSAGE: line 8: Error: Out of memory JSRegress/Int32Array-alloc-huge-long-lived On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE". -PASS no exception thrown -PASS successfullyParsed is true +FAIL caught exception: Error: Out of memory +FAIL successfullyParsed should be true (of type boolean). Was undefined (of type undefined). TEST COMPLETE
Also (flaky): js/dfg-int16array.html js/dom/create-lots-of-workers.html js/regress/array-prototype-map.html js/regress/ArrayBuffer-Int8Array-alloc-long-lived.html js/slow-stress/Int32Array-alloc-huge.html js/slow-stress/variadic-closure-call.html js/slow-stress/array-prototype-filter.html In many cases they alternate between failures and crashes.
<rdar://problem/19618597>