Skip to content

Clarify physical page exhaustion #632

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
merged 1 commit into from
Mar 31, 2016
Merged

Clarify physical page exhaustion #632

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 3 additions & 0 deletions Nondeterminism.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down