I have memory limits turned off anyway, because it used to be that if I ran something that triggered a planet package install the memory limit would crash the install and leave my planet cache in a bad state. It may be that's no longer the case, and I should put the memory limit back on. Nevertheless, since I run with unlimited memory, the fact that I ran out before I hit an artificial limit doesn't indicate where the bug happened.
--Carl On Thu, Feb 19, 2009 at 4:34 PM, Robby Findler <robby at eecs.northwestern.edu> wrote: > I asked because check syntax doesn't install memory limits when it > runs, only run does. Perhaps your tool is doing the same thing? > > Robby > > On Thu, Feb 19, 2009 at 2:58 PM, Carl Eastlund <cce at ccs.neu.edu> wrote: >> No, though I might have just triggered the theorem prover, which uses >> the same hook to compile the program as check syntax >> (drscheme:eval:expand-program), if that's relevant. >> >> --Carl >> >> On Thu, Feb 19, 2009 at 3:32 PM, Robby Findler >> <robby at eecs.northwestern.edu> wrote: >>> Were you running check syntax? >>> >>> Robby >>> >>> On Thu, Feb 19, 2009 at 2:28 PM, Carl Eastlund <cce at ccs.neu.edu> wrote: >>>> DrScheme gave me the error message in the subject -- I wish I had >>>> copied or screenshotted it, but I was so surprised to see it I just >>>> clicked "OK" to see what it would do, so I may have the wording >>>> slightly wrong. Anyway, DrScheme promptly crashed (and Mac OS gave me >>>> to "quit unexpectedly dialog") when I hit "OK". >>>> >>>> I don't recall doing anything intensive when that happened, I was just >>>> running a program I had run before (in Dracula). Anyone know what >>>> might have happened, or what further information I should look for to >>>> help diagnose this? >>>> >>>> -- >>>> Carl Eastlund
