[racket-dev] Memory grows without bound compiling tool-lib-extract.rkt

On Jun 3, Sam Tobin-Hochstadt wrote: > > A quick `git bisect' (a great tool, btw) suggests that commit > ac69f11 caused the problem. That's unlikely to be the cause -- only exposing some other bug. IIRC, the bisect tool can work on certain paths only, and this would be more useful here (and more

[racket-dev] Memory grows without bound compiling tool-lib-extract.rkt

On Thu, Jun 3, 2010 at 12:53 PM, Matthew Flatt wrote: > At Thu, 3 Jun 2010 12:49:27 -0400, Sam Tobin-Hochstadt wrote: >> Currently, the following command: >> >> ?raco make collects/scribblings/tools/tool-lib-extract.rkt >> >> rapidly consumes all available memory, and has to be killed manually. >

[racket-dev] Memory grows without bound compiling tool-lib-extract.rkt

Currently, the following command: raco make collects/scribblings/tools/tool-lib-extract.rkt rapidly consumes all available memory, and has to be killed manually. -- sam th samth at ccs.neu.edu

[racket-dev] Memory grows without bound compiling tool-lib-extract.rkt

At Thu, 3 Jun 2010 13:00:45 -0400, Eli Barzilay wrote: > On Jun 3, Sam Tobin-Hochstadt wrote: > > > > A quick `git bisect' (a great tool, btw) suggests that commit > > ac69f11 caused the problem. > > That's unlikely to be the cause -- only exposing some other bug. Right. Although `bisect' corre

[racket-dev] Memory grows without bound compiling tool-lib-extract.rkt

At Thu, 3 Jun 2010 12:49:27 -0400, Sam Tobin-Hochstadt wrote: > Currently, the following command: > > raco make collects/scribblings/tools/tool-lib-extract.rkt > > rapidly consumes all available memory, and has to be killed manually. I'm working on it.