I don't use the gui framework at all. This is all just pounding on global 
hash-tables and vectors. Or are you talking about the sandbox queuing up 
----- Original Message -----
From: "Robby Findler" <ro...@eecs.northwestern.edu>
To: "J. Ian Johnson" <i...@ccs.neu.edu>
Cc: "dev" <dev@racket-lang.org>
Sent: Monday, September 9, 2013 1:16:51 PM GMT -05:00 US/Canada Eastern
Subject: Re: [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? 


On Mon, Sep 9, 2013 at 10:54 AM, J. Ian Johnson < i...@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? 

Racket Developers list: 

  Racket Developers list:

Reply via email to