<div dir="ltr">OK, will do. If I see anything I will post it.<div> </div><div style>Regards,</div><div style>-joe</div></div><div class="gmail_extra"> <div class="gmail_quote">On Mon, Feb 25, 2013 at 10:52 AM, Matthew Flatt <<a href="mailto:mflatt@cs.utah.edu" target="_blank">mflatt@cs.utah.edu</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thanks --- knowing that it looks like a frozen process instead of a memory fault is useful. If you start DrRacket in a terminal as racket -l drracket then, when DrRacket get stuck again, there's a small chance that typing Ctl-C in the terminal will produce a useful context listing. It's probably worth a try, anyway. <div class="HOEnZb"><div class="h5"> At Mon, 25 Feb 2013 10:29:19 -0800, Joe Gilray wrote: > No problem, Matthew, I know that I've been less-than-specific, here's what > I can say: > > Since 5.3.2, I've seen about 7 crashes, they all act the same: Win7 > suddenly says "the program is not responding". At least twice it's > happened when I hit the debugger button in DrRacket. Otherwise it feels > random (at least once when clicking on the definitions window, at least > once when simply running a program in the interactions pane). > > Thanks, > -Joe > > > On Mon, Feb 25, 2013 at 10:15 AM, Matthew Flatt <<a href="mailto:mflatt@cs.utah.edu">mflatt@cs.utah.edu</a>> wrote: > > > FWIW, I'm not ignoring your reports of crashes on 64-bit Windows, but I > > haven't yet done enough work on it. I'm still looking for a way to > > provoke crashes, and the thought that the debugger might be relevant is > > helpful. > > > > At Mon, 25 Feb 2013 10:08:59 -0800, Joe Gilray wrote: > > > I had a problem with my test code that led me to believe that the 64-bit > > > version of 5.3.3 was faster than the 32-bit version... to paraphrase SNL > > > from the good old days: "never mind." > > > > > > I still do see crashes on the 64-bit version and not on 32-bit: The > > > crashes still seem random, but do seem to occur more often in the > > debugger. > > > > > > Regards, > > > -Joe > > > > > > > > > On Tue, Feb 19, 2013 at 7:10 PM, Joe Gilray <<a href="mailto:jgilray@gmail.com">jgilray@gmail.com</a>> wrote: > > > > > > > Has anyone else noticed that the 64-bit version on Win7 is faster than > > the > > > > 32-bit version? > > > > > > > > I thought that the longer pointers were supposed to slow down > > execution. > > > > > > > > BTW, still seeing some crashes on 64-bit and none on 32-bit > > > > > > > > Thoughts? > > > > -Joe > > > > > > > > > > > > On Sat, Feb 16, 2013 at 10:49 AM, Joe Gilray <<a href="mailto:jgilray@gmail.com">jgilray@gmail.com</a>> > > wrote: > > > > > > > >> Thanks Racketeers, > > > >> > > > >> I am still seeing crashes on Win7 64bit with 5.3.3. About every 6 > > hours > > > >> or so I get "program not responding" (doesn't seem to correlate to > > anything > > > >> in particular). > > > >> > > > >> Haven't seen it on Win7 32 bit. > > > >> > > > >> -Joe > > > >> > > > >> > > > >> On Fri, Feb 15, 2013 at 12:53 PM, Eli Barzilay <<a href="mailto:eli@barzilay.org">eli@barzilay.org</a>> > > wrote: > > > >> > > > >>> Racket version 5.3.3 is now available from > > > >>> > > > >>> <a href="http://racket-lang.org/" target="_blank">http://racket-lang.org/</a> > > > >>> > > > >>> This is a bug-fix release to address a flaw in DrRacket v5.3.2 > > > >>> concerning interactions between the contour window and the syntax > > > >>> coloring. > > > >>> > > > >>> Feedback Welcome, > > > >>> -- > > > >>> ((lambda (x) (x x)) (lambda (x) (x x))) Eli > > Barzilay: > > > >>> <a href="http://barzilay.org/" target="_blank">http://barzilay.org/</a> Maze is > > Life! > > > >>> ____________________ > > > >>> Racket Users list: > > > >>> <a href="http://lists.racket-lang.org/users" target="_blank">http://lists.racket-lang.org/users</a> > > > >>> > > > >> > > > >> > > > > > > > ____________________ > > > Racket Users list: > > > <a href="http://lists.racket-lang.org/users" target="_blank">http://lists.racket-lang.org/users</a> > > </div></div></blockquote></div> </div>