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

2013-09-11 Thread J. Ian Johnson
Johnson i...@ccs.neu.edu To: David Vanderson david.vander...@gmail.com Cc: dev dev@racket-lang.org, J. Ian Johnson i...@ccs.neu.edu Sent: Monday, September 9, 2013 2:01:02 PM GMT -05:00 US/Canada Eastern Subject: Re: [racket-dev] call-with-limits memory bound isn't actually bounding memory usage Ah

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

2013-09-11 Thread Robby Findler
Subject: Re: [racket-dev] call-with-limits memory bound isn't actually bounding memory usage Ah, that would probably be the problem. Without having to modify too much code, would the proper way to call a function entirely within the sandbox be to use dynamic-require in the thunk, rather than

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

2013-09-11 Thread J. Ian Johnson
/Canada Eastern Subject: Re: [racket-dev] call-with-limits memory bound isn't actually bounding memory usage Ah, that would probably be the problem. Without having to modify too much code, would the proper way to call a function entirely within the sandbox be to use dynamic-require

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

2013-09-11 Thread J. Ian Johnson
Sent: Monday, September 9, 2013 2:01:02 PM GMT -05:00 US/Canada Eastern Subject: Re: [racket-dev] call-with-limits memory bound isn't actually bounding memory usage Ah, that would probably be the problem. Without having to modify too much code, would the proper way to call a function

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

2013-09-11 Thread Robby Findler
:50 PM GMT -05:00 US/Canada Eastern Subject: Re: [racket-dev] call-with-limits memory bound isn't actually bounding memory usage Just so we're clear, this should not OOM, but rather print #t? #lang racket/load (module A racket (provide global go) (define global '()) (define (go) (set

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

2013-09-11 Thread Eli Barzilay
An hour ago, J. Ian Johnson wrote: Okay, stamourv made your response make sense. I added parameterize ([current-namespace (make-base-namespace)]) inside the thunk, [...] If you're going down that road (which makes sense, of course), then it would probably be much easier to just use the full

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

2013-09-09 Thread Carl Eastlund
Does run-analysis have the form (lambda () actually-run-analysis)? Because if not, that's the problem. Carl Eastlund -- WARNING! Poorly-typed cell phone email precedes. On Sep 9, 2013 11:55 AM, J. Ian Johnson i...@ccs.neu.edu wrote: I'm running my analysis benchmarks in the context of

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

2013-09-09 Thread J. Ian Johnson
the usage over the limit. -Ian - Original Message - From: Carl Eastlund carl.eastl...@gmail.com To: J. Ian Johnson i...@ccs.neu.edu Cc: dev dev@racket-lang.org Sent: Monday, September 9, 2013 12:05:21 PM GMT -05:00 US/Canada Eastern Subject: Re: [racket-dev] call-with-limits memory bound

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

2013-09-09 Thread Carl Eastlund
Eastlund carl.eastl...@gmail.com To: J. Ian Johnson i...@ccs.neu.edu Cc: dev dev@racket-lang.org Sent: Monday, September 9, 2013 12:05:21 PM GMT -05:00 US/Canada Eastern Subject: Re: [racket-dev] call-with-limits memory bound isn't actually bounding memory usage Does run-analysis have the form

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

2013-09-09 Thread Robby Findler
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 i...@ccs.neu.edu

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

2013-09-09 Thread David Vanderson
. Ian Johnson i...@ccs.neu.edu Cc: dev dev@racket-lang.org Sent: Monday, September 9, 2013 1:50:13 PM GMT -05:00 US/Canada Eastern Subject: Re: [racket-dev] call-with-limits memory bound isn't actually bounding memory usage Just to make sure, is the memory being allocated reachable from outside

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

2013-09-09 Thread Robby Findler
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

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

2013-09-09 Thread J. Ian Johnson
-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

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

2013-09-09 Thread J. Ian Johnson
Vanderson david.vander...@gmail.com To: J. Ian Johnson i...@ccs.neu.edu Cc: dev dev@racket-lang.org Sent: Monday, September 9, 2013 1:50:13 PM GMT -05:00 US/Canada Eastern Subject: Re: [racket-dev] call-with-limits memory bound isn't actually bounding memory usage Just to make sure, is the memory

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

2013-09-09 Thread David Vanderson
] 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