diff options
| author | JF Bastien <github@jfbastien.com> | 2016-03-31 15:37:53 -0700 |
|---|---|---|
| committer | JF Bastien <github@jfbastien.com> | 2016-03-31 15:37:53 -0700 |
| commit | 675eee78ea4613025ec3bd12f0020609bfb8c81a (patch) | |
| tree | 2ec20767ce53d458b14b21585e4c0ff45176d8cd | |
| parent | 5b91ef68a3fbcf0655e6c3e21d0f87e6cdfc0c58 (diff) | |
| download | nanowasm-design-675eee78ea4613025ec3bd12f0020609bfb8c81a.tar.gz | |
Clarify physical page exhaustion
As discussed in https://github.com/WebAssembly/design/pull/629#discussion_r58138148
| -rw-r--r-- | Nondeterminism.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/Nondeterminism.md b/Nondeterminism.md index 38cc577..d393ae7 100644 --- a/Nondeterminism.md +++ b/Nondeterminism.md @@ -45,6 +45,9 @@ currently admits nondeterminism: may vary between platforms. * Environment-dependent resource limits may be exhausted. A few examples: - Memory allocation may fail. + - The runtime can fail to allocate a physical page when a memory location is first + accessed (e.g. through a load or store), even if that memory was virtually reserved + by the maximum size property of the [memory section](Module.md#linear-memory-section). - Program stack may get exhausted (e.g., because function call depth is too big, or functions have too many locals, or infinite recursion). Note that this stack isn't located in the program-accessible linear memory. |