[racket] Getting unusual behavior from racket/sandbox: not truly capping memory usage?!

I don't understand it either, but I'm glad you found it.

On Mon, Apr 22, 2013 at 2:10 PM, Danny Yoo <dyoo at hashcollision.org> wrote:
> Tracked it.  There's something funky going on with poll-or-spawn, right here:
>
>     https://github.com/plt/racket/blob/master/collects/racket/port.rkt#L1122-L1125
>
> I don't quite understand what's going on here yet, but the highlighted
> thread is always blocking on nack, and never gets killed.  It's this
> thread that's accumulating in the loop of:
>
>     #lang racket
>     (define ip (open-input-string "hello world"))
>     (define evt (peek-bytes-evt 1 0 #f ip))
>     (let loop ()
>       (sync (handle-evt evt
>                         (lambda (res)
>                           (loop)))))



-- 
Jay McCarthy <jay at cs.byu.edu>
Assistant Professor / Brigham Young University
http://faculty.cs.byu.edu/~jay

"The glory of God is Intelligence" - D&C 93