From 675eee78ea4613025ec3bd12f0020609bfb8c81a Mon Sep 17 00:00:00 2001 From: JF Bastien Date: Thu, 31 Mar 2016 15:37:53 -0700 Subject: [PATCH] Clarify physical page exhaustion As discussed in https://github.com/WebAssembly/design/pull/629#discussion_r58138148 --- Nondeterminism.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Nondeterminism.md b/Nondeterminism.md index 38cc577b..d393ae72 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.