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
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
/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
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
: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
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
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
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
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
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
. 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
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
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
-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
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
] 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
16 matches
Mail list logo
