F5 compiling behavior different than pressing the run button

[dyoo]

There's some state that is not being reset correctly. Under Racket, if you press F5 several times (seven) for the following code:

(

(define (f x)
  (* x x))

you'll get a bad error message eventually: "WeScheme appears to be busy or unavailable at this time. Please try again later."

Whereas if you press the run button, I haven't seen this error occur.

I'm investigating whether or not it has to do with xmlhttprequest and internal browser throttling...

[schanzer]

This is no longer reproducible (likely due to the object-code caching that Danny implemented this Spring). CLOSE