One thing that might help is if, during the pause, you open up a terminal, figure out the pid for the drracket's misbehaving and then do "kill -SIGINT <pid>" you might get a message with a stack in it. I'm not completely sure about this, but if you start up from the shell (not using "open" but by running something like "/Applications/Racket\ v6.4/bin/drracket ") and then do control-c in the shell you should see a message there. That should be the same as SIGINT, I think.
The stack trace from the break exn will be a helpful clue in figuring out what is going on here. Robby On Mon, Feb 22, 2016 at 2:04 PM, 'John Clements' via Racket Users <racket-users@googlegroups.com> wrote: > I have several students who are observing truly impressive UI delays in using > DrRacket. Specifically, it often happens when they type a double-quote (“) > with “automatic parentheses” enabled, and after typing the key, it will take > more than 16 seconds for the screen to update and for the quotes to appear. > The delay seems to be shortened significantly by clicking or hitting the > arrow keys, and I suspect this may be related to OS X’s “app nap” feature, > that will shut down an application when it thinks that it doesn’t need > foreground processing. > > Any ideas? > > John > > > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
