Skip to content

fix: wasm_memory_threshold is now bounded by 256TiB #304

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mraszyk merged 2 commits into from
Jul 6, 2026
+3 −2
Merged

fix: wasm_memory_threshold is now bounded by 256TiB #304

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8369da4
fix: wasm_memory_threshold is now bounded by 256TiB
mraszyk Jun 26, 2026
021c88d
Merge branch 'main' into mraszyk/max-wasm-memory-threshold
mraszyk Jul 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/references/ic-interface-spec/changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,7 @@ sidebar:
delegations are not accepted; the value `"all"` permits all kinds of requests, same as
omitting the field. Requests of any kind carrying a delegation with any other value of
the `permissions` field are not accepted.
* `wasm_memory_threshold` in canister settings is now bounded by 2<sup>48</sup>, analogously to `wasm_memory_limit`.

### 0.63.0 (2026-06-29) {$0_63_0}
* Support for the HTTP method `PATCH` in canister `http_request` in non-replicated mode.
Expand Down
4 changes: 2 additions & 2 deletions docs/references/ic-interface-spec/management-canister.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,7 +79,7 @@ The optional `settings` parameter can be used to set the following settings:

- `wasm_memory_limit` (`nat`)

Must be a number between 0 and 2<sup>48</sup>-1 (i.e., 256TB), inclusively, and indicates the upper limit on the WASM heap memory consumption of the canister in bytes.
Must be a number between 0 and 2<sup>48</sup>, inclusively, and indicates the upper limit on the WASM heap memory consumption of the canister in bytes.

An operation (update method, canister init, canister post_upgrade) that causes the WASM heap memory consumption to exceed this limit will trap.
The WASM heap memory limit is ignored for query methods, response callback handlers, global timers, heartbeats, and canister pre_upgrade.
Expand Down Expand Up @@ -115,7 +115,7 @@ The optional `settings` parameter can be used to set the following settings:

- `wasm_memory_threshold` (`nat`)

Must be a number between 0 and 2<sup>64</sup>-1, inclusively, and indicates the threshold on the remaining wasm memory size of the canister in bytes:
Must be a number between 0 and 2<sup>48</sup>, inclusively, and indicates the threshold on the remaining wasm memory size of the canister in bytes:
if the remaining wasm memory size of the canister is below the threshold, execution of the ["on low wasm memory" hook](./canister-interface.md#on-low-wasm-memory) is scheduled.

Default value: 0 (i.e., the "on low wasm memory" hook is never scheduled).
Expand Down
Loading