[wasm] Throw a RangeError if Wasm memory could not be allocated.

test/mjsunit/regress/wasm/regression-666741.js

Index: test/mjsunit/regress/wasm/regression-666741.js
diff --git a/test/mjsunit/regress/wasm/regression-666741.js b/test/mjsunit/regress/wasm/regression-666741.js
new file mode 100644
index 0000000000000000000000000000000000000000..5a4f19875a28d9eb7e1e739530e7005131d84440
--- /dev/null
+++ b/test/mjsunit/regress/wasm/regression-666741.js
@@ -0,0 +1,15 @@
+// Copyright 2016 the V8 project authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+//
+// Flags: --random-seed=-1101427159 --enable-slow-asserts --expose-wasm
+
+(function __f_7() {
+  try {

[titzer, 2016/11/18 23:19:29]

You can use one of the assertThrows() helper functions here I think.

[Eric Holk, 2016/11/21 21:15:15]

Done.

I didn't use assertThrows originally because I wanted to test the behavior that
if WebAssembly.Memory throws, it throws a RangeError, without requiring it to
throw. I don't think there's anything in the WebAssembly spec to require failure
here, it's just a quirk of V8's implementation. It'll be easy enough to fix in
the future if we remove this restriction though.

+    let memory = new WebAssembly.Memory({initial: 59199});
+  } catch (e) {
+    if (!(e instanceof RangeError)) {
+      throw e;
+    }
+  }
+})();