[racket-dev] call-with-limits memory bound isn't actually bounding memory usage

From: J. Ian Johnson (ianj at ccs.neu.edu)
Date: Mon Sep 9 11:54:34 EDT 2013

I'm running my analysis benchmarks in the context of (with-limits (* 30 60) 2048 <run-analysis>), and it's been good at killing the process when the run should time out, but now I have an instantiation of the framework that just gobbles up 15GiB of memory without getting killed. What might be going on here?


Posted on the dev mailing list.