[racket-dev] weird (memory?) bug using (dis)similar require mechanisms

At Fri, 09 Sep 2011 12:29:13 +0200, Marijn wrote:
> this racket bug was discovered when I was trying out geiser which
> starts programs in a way that exposes this bug. The program starts
> correctly but none of the buttons work (or only reserve screen space)
> and it is hard to terminate the program.

I think this is now fixed. For me, the GUI worked until I clicked a
button that needed to grow the frame, at which point it got stuck due
to competing callbacks with different opinions on the frame height.
(One of those callbacks was wrong.)

Although it's not directly related, I also changed the way `on-size'
and `on-move' callbacks are queued to put them at the right priority. I
think that change will solve the problem that Neil has long reported,
where DrRacket would take a long time to catch up if you dragged a
resize border around a lot.