There appears to be a race condition in console output event. For instance, typing 'help' to show the function as the first command after loading on my Powerbook results in double output (half black, half blue) that kills the console for further input and the following error in the console: 2004-11-01 11:06:56.372 R[681] *** NSTimer discarding exception 'NSRangeException' (reason '*** NSRunStorage, _NSBlockNumberForIndex(): index (2919) beyond array bounds (2000)') that raised during firing of timer with target 3ace80 and selector 'runRELP:' However, doing some stuff and then trying the same command doesn't result in the same problem. Either its just the particular timing of the event or something about the startup process that causes the problem. In any case, I expect it will be hard to replicate, but a showstopper when it happens to people. Just a heads up. --- Byron Ellis (ellis@stat.harvard.edu) "Oook" -- The Librarian
weird race condition bug.
2 messages · Byron Ellis, Simon Urbanek
On Nov 1, 2004, at 2:12 PM, Byron Ellis wrote:
There appears to be a race condition in console output event. For instance, typing 'help' to show the function as the first command after loading on my Powerbook results in double output (half black, half blue) that kills the console for further input and the following error in the console: 2004-11-01 11:06:56.372 R[681] *** NSTimer discarding exception 'NSRangeException' (reason '*** NSRunStorage, _NSBlockNumberForIndex(): index (2919) beyond array bounds (2000)') that raised during firing of timer with target 3ace80 and selector 'runRELP:'
It's not quite clear what happens there - I can reproduce this on my PowerBook, too. However, it's not really a show-stopper, because hitting <Esc> will give you console back and everything is OK again. It's hard to tell if this is related to the timer (we're using a one-shot timer to start the REPL), or something else ... I'll keep on digging ... Simon