suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

clarification on the (new) way memory is charged

Browse Source 
svn: r12856
This commit is contained in:
Eli Barzilay 2008-12-15 18:22:58 +00:00
parent 04d0b55134
commit b0758de6f1
1 changed files with 8 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
collects/scribblings/reference/sandbox.scrbl
View File

@ -514,7 +514,14 @@ this limit is exceeded, the sandbox is terminated. This value is used
when the sandbox is created and the limit cannot be changed
afterwards. It defaults to 30mb. See @scheme[sandbox-eval-limits]
for per-evaluation limits and a description of how the two limits work
together.}
together.
Note that (when memory accounting is enabled) memory is attributed to
the highest custodian that refers to it. This means that if you
inspect a value that sandboxed evaluation returns outside of the
sandbox, your own custodian will be charged for it. To ensure that it
is charged back to the sandbox, you should remove references to such
values when the code is done inspecting it.}
@defparam[sandbox-eval-limits limits