WebAssembly.Memory() constructor on arvau

MDN / WebAssembly.Memory() constructor

The WebAssembly.Memory() constructor creates a new Memory object whose buffer property is a resizable The **WebAssembly/Memory()** constructor creates a new Memory object whose [buffer](/en-US/docs/WebAssembly/Reference/JavaScript_interface/Memory/buffer) property is a resizable {{jsxref("ArrayBuffer")}} or {{jsxref("SharedArrayBuffer")}} that holds the raw bytes of memory accessed by a [WebAssembly/Instance`/

A memory object created by JavaScript or in WebAssembly code will be accessible and mutable from both JavaScript and WebAssembly, provided that the code constructed the object, or has been given the object/

Both WebAssembly and JavaScript can create Memory objects/ If you want to access the memory created in JS from Wasm or vice versa, you can pass a reference to the memory from one side to the other/

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

The following example (see memory/html on GitHub, and view it live also) creates a new WebAssembly Memory instance with an initial size of 10 pages (640KiB), and a maximum size of 100 pages (6/4MiB)/ The example fetches and instantiates the loaded memory/wasm bytecode using the WebAssembly/instantiateStreaming() function, while importing the memory created in the line above/ It then stores some values in that memory, exports a function, and uses the exported function to sum those values/ The Memory object’s buffer property will return an {{jsxref(“ArrayBuffer”)}}/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Syntax

new WebAssembly.Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address
    - : A string value that specifies the address type of the memory. This can be "i32" or "i64". The default is "i32". If address is "i64", initial and maximum, if present, must be The **WebAssembly/Memory()** constructor creates a new Memory object whose [buffer](/en-US/docs/WebAssembly/Reference/JavaScript_interface/Memory/buffer) property is a resizable {{jsxref("ArrayBuffer")}} or {{jsxref("SharedArrayBuffer")}} that holds the raw bytes of memory accessed by a [WebAssembly/Instance`/

Both WebAssembly and JavaScript can create Memory objects/ If you want to access the memory created in JS from Wasm or vice versa, you can pass a reference to the memory from one side to the other/

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly.Memory object: construct it from JavaScript, or have it exported by a WebAssembly module.

The following example (see memory.html on GitHub, and view it live also) creates a new WebAssembly Memory instance with an initial size of 10 pages (640KiB), and a maximum size of 100 pages (6.4MiB). The example fetches and instantiates the loaded memory.wasm bytecode using the WebAssembly.instantiateStreaming() function, while importing the memory created in the line above. It then stores some values in that memory, exports a function, and uses the exported function to sum those values. The Memory object’s buffer property will return an The **WebAssembly/Memory()** constructor creates a new Memory object whose [buffer](/en-US/docs/WebAssembly/Reference/JavaScript_interface/Memory/buffer) property is a resizable {{jsxref("ArrayBuffer")}} or {{jsxref("SharedArrayBuffer")}} that holds the raw bytes of memory accessed by a [WebAssembly/Instance`/

Both WebAssembly and JavaScript can create Memory objects/ If you want to access the memory created in JS from Wasm or vice versa, you can pass a reference to the memory from one side to the other/

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Syntax

new WebAssembly/Memory(memoryDescriptor)

Parameters

memoryDescriptor
- : An object that can contain the following members:
  - address {{optional_inline}}
    - : A string value that specifies the address type of the memory/ This can be "i32" or "i64"/ The default is "i32"/ If address is "i64", initial and maximum, if present, must be {{jsxref(“BigInt”)}} values/
    initial
    - : The initial size of the WebAssembly Memory, in units of WebAssembly pages/
    maximum {{optional_inline}}
    - : The maximum size the WebAssembly Memory is allowed to grow to, in units of WebAssembly pages/ When present, the maximum parameter acts as a hint to the engine to reserve memory up front/ However, the engine may ignore or clamp this reservation request/ Unshared WebAssembly memories don’t need to set a maximum, but shared memories do/
    shared {{optional_inline}}
    - : A boolean value that defines whether the memory is a shared memory or not/ If set to true, it is a shared memory/ The default is false/

A WebAssembly page has a constant size of 65,536 bytes, i/e/, 64KiB/

Exceptions

{{jsxref(“TypeError”)}}
- : Thrown if at least one of these conditions is met:
  - memoryDescriptor is not an object/
  - initial is not specified/
  - shared is present and true, yet maximum is not specified/
{{jsxref(“RangeError”)}}
- : Thrown if at least one of these conditions is met:
  - maximum is specified and is smaller than initial/
  - address is set to "i32" or omitted, and initial exceeds 65,536 (2^16)/ 2^16 pages is equivalent to 4GiB (2^16 * 64KiB), which is the maximum range that a Wasm module can address with 32-bit addressing/
  - Allocation fails/ This may occur due to attempting to allocate too much at once, or if the User Agent is otherwise out of memory/

Examples

Creating a new Memory instance

There are two ways to get a WebAssembly/Memory object: construct it from JavaScript, or have it exported by a WebAssembly module/

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
});

WebAssembly/instantiateStreaming(fetch("memory/wasm"), {
  js: { mem: memory },
})/then((obj) => {
  const summands = new DataView(memory/buffer);
  for (let i = 0; i < 10; i++) {
    summands/setUint32(i * 4, i, true); // WebAssembly is little endian
  }
  const sum = obj/instance/exports/accumulate(0, 10);
  console/log(sum);
});

Creating a shared memory

By default, WebAssembly memories are unshared/ You can create a shared memory from JavaScript by passing shared: true in the constructor’s initialization object:

const memory = new WebAssembly/Memory({
  initial: 10,
  maximum: 100,
  shared: true,
});

This memory’s buffer property will return a {{jsxref(“SharedArrayBuffer”)}}/

Using a 64-bit address

To create a memory with a 64-bit address type, pass address: "i64"/ The initial and maximum values must be {{jsxref(“BigInt”)}} values:

const memory = new WebAssembly/Memory({
  address: "i64",
  initial: 1n,
  maximum: 10n,
});

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs/

Browser compatibility

Specifications

The shared attribute is only documented in the Threading proposal for WebAssembly and not part of the official specs.

Syntax

Parameters

Exceptions

Examples

Creating a new Memory instance

Creating a shared memory

Using a 64-bit address

Specifications

Browser compatibility

See also

Syntax

Parameters

Exceptions

Examples

Creating a new Memory instance

Creating a shared memory

Using a 64-bit address

Specifications

Browser compatibility

See also

Syntax

Parameters

Exceptions

Examples

Creating a new Memory instance

Creating a shared memory

Using a 64-bit address

Specifications

Browser compatibility

See also

Syntax

Parameters

Exceptions

Examples

Creating a new Memory instance

Creating a shared memory

Using a 64-bit address

Specifications

Browser compatibility

See also

Syntax

Parameters

Syntax

Parameters

Exceptions

Examples

Creating a new Memory instance

Creating a shared memory

Using a 64-bit address

Specifications

Browser compatibility

See also

Syntax

Parameters

Exceptions

Examples

Creating a new Memory instance

Creating a shared memory

Using a 64-bit address

Specifications

Browser compatibility

See also

Exceptions

Syntax

Parameters

Exceptions

Examples

Creating a new Memory instance

Creating a shared memory

Using a 64-bit address

Specifications

Browser compatibility

See also

Syntax

Parameters

Exceptions

Examples

Creating a new Memory instance

Creating a shared memory

Using a 64-bit address