Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(9)

Unified Diff: test/mjsunit/big-array-literal.js

Issue 2596673002: [test] Avoid stack space exhaustion in test by passing --no-lazy (Closed)
Patch Set: Proper diff Created 4 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: test/mjsunit/big-array-literal.js
diff --git a/test/mjsunit/big-array-literal.js b/test/mjsunit/big-array-literal.js
index 19d1ff406db8a07783e90b8474baa376fc0ba894..624e9b704de87c27f8b7cc559fc7870105178e07 100644
--- a/test/mjsunit/big-array-literal.js
+++ b/test/mjsunit/big-array-literal.js
@@ -28,6 +28,11 @@
// On MacOS X 10.7.5, this test needs a stack size of at least 788 kBytes.
// On PPC64, this test needs a stack size of at least 698 kBytes.
// Flags: --stack-size=1000
+//
+// The above stack limits were written assuming no lazy parsing, so turn
+// off lazy parsing for this test.
+// See https://bugs.chromium.org/p/v8/issues/detail?id=5729 for details.
+// Flags: --no-lazy
// Test that we can make large object literals that work.
// Also test that we can attempt to make even larger object literals without
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698