Then I think that that means that the message came from rep.rkt's no-user-evaluation-message function and that you either should have gotten a dialog with an explanation for why it terminated, or you have the preference 'drracket:show-killed-dialog set to #f. I think that the only two explanations are that 'exit' was called or that your ran out of memory, but it may also be the case that you'd get a dialog with no explanation. This could happen with this program, for example:
#lang racket (custodian-shutdown-all (current-custodian)) or this one: #lang racket (kill-thread (current-thread)) Or, it may be the case that you'd get a dialog with no explanation when you ran out of memory, if there's a bug (race-condition or something possibly). I don't see how you'd get the yellow/black warning message without getting a dialog, tho, unless you have that pref set. Not much help, I know. Sorry. Robby On Mon, Oct 7, 2013 at 10:52 AM, Neil Toronto <neil.toro...@gmail.com>wrote: > Black on yellow. > > > On 10/07/2013 09:50 AM, Robby Findler wrote: > >> Was it black on yellow or red? >> >> Robby >> >> >> On Mon, Oct 7, 2013 at 10:32 AM, Neil Toronto <neil.toro...@gmail.com >> <mailto:neil.toro...@gmail.com**>> wrote: >> >> I have a long-running random simulation that spits out debug >> messages. I extrapolated that it would take 20 hours to get >> 5,000,000 samples, and let it run for a day. Here's what I saw when >> I returned: >> >> >> Welcome to DrRacket, version 5.90.0.9--2013-10-04(876995d5/**__d) >> [3m]. >> >> Language: typed/racket [custom]; memory limit: 1024 MB. >> starting... >> sample-search-tree returned failure >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> i = 100 >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> >> [...] >> >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> i = 2605500 >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> refinement-sample-point returned #f >> >> Interactions disabled >> | >> >> 560157:0 720.77MB >> >> >> Fear my ASCII art status bar. >> >> "720.77MB" is what I got after clicking the GC indicator. (Before, >> it was about 300MB.) There were no command-line messages from >> DrRacket. >> >> I don't think this is an out-of-memory problem. DrRacket has been >> good about asking for more during other simulations, my limit is set >> to 1024MB, and I really doubt I'm allocating a 304MB temporary object. >> >> I wrote a small program to print 600000 debug messages, thinking it >> was a limit on the number of lines in the REPL, and it ran to >> completion. >> >> For full disclosure: I paused and restarted DrRacket from the >> command line (fg; ctrl-z; bg) a few times while the simulation was >> running, so I could use my laptop unplugged without draining the >> battery. >> >> Besides running out of memory, what else could cause a program to >> halt with "Interactions disabled", and how can I avoid it? >> >> Neil ⊥ >> _________________________ >> Racket Developers list: >> http://lists.racket-lang.org/_**_dev<http://lists.racket-lang.org/__dev>< >> http://lists.racket-lang.org/**dev <http://lists.racket-lang.org/dev>> >> >> >> >
_________________________ Racket Developers list: http://lists.racket-lang.org/dev
