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

The framework will, sometimes do stuff that queues callbacks and, depending
on how you've set up other things, the code running there might escape from
the limit. Did you try putting the eventspace under the limit too?

Robby


On Mon, Sep 9, 2013 at 10:54 AM, J. Ian Johnson <ianj at ccs.neu.edu> wrote:

> 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?
>
> Running 5.90.0.9
> -Ian
> _________________________
>   Racket Developers list:
>   http://lists.racket-lang.org/dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/dev/archive/attachments/20130909/1315d8e8/attachment.html>