Custodian memory limit accounting varies by Racket backend
Designing per-evaluation resource containment in Racket with custodians and racket/sandbox requires a memory cap that reliably triggers an out-of-memory condition inside the contained computation while leaving the host process intact. The documented mechanism uses custodian-limit-memory and call-with-limits/with-limits. Memory accounting is described as appr
racket