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

From: Danny Yoo (dyoo at hashcollision.org)
Date: Mon Apr 22 16:31:52 EDT 2013

Ok, good!  Matthew Flatt is investigating.

It looks like something like:


can clear the memory leak, but mflatt says that we shouldn't have to
do this, that the VM should automatically kill the monitoring thread
once it detects the nack is inaccessible.  This is totally out of my
domain, but thankfully he's on it now.  :)

Posted on the users mailing list.