fac176d813
For memory limit checks, we should use the minimum of the --wasm-max-mem-pages flag and kV8MaxWasmMemoryPages. The former is a limit set by the user, the latter is the maximum we can handle internally. R=titzer@chromium.org Bug: chromium:898677 Change-Id: I3c549f4e90dd016b5d07475d9353f30134f76dcc Reviewed-on: https://chromium-review.googlesource.com/c/1305274 Commit-Queue: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Ben Titzer <titzer@chromium.org> Cr-Commit-Position: refs/heads/master@{#57127}
14 lines
417 B
JavaScript
14 lines
417 B
JavaScript
// Copyright 2018 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: --wasm-max-mem-pages=49152
|
|
|
|
let mem = new WebAssembly.Memory({initial: 1});
|
|
try {
|
|
mem.grow(49151);
|
|
} catch (e) {
|
|
// This can fail on 32-bit systems if we cannot make such a big reservation.
|
|
if (!(e instanceof RangeError)) throw e;
|
|
}
|