fatal error

Nicholas,

How did you get such error? May be you have plugged/unplugged additional monitor?

Hi Roman,

I do use a second monitor (a third through synergy, though I can't see how that would interfere). The error happened in the morning, it might have been when I was plugging everything in or dragging Rubymine across screens. I can't say for sure though.

I get a few of these exceptions (well, less as time goes on and your build becomes more stable), and I generally ignore them out of laziness. I'll report them a bit more if it will be helpful.

Regards,
Nicholas

Hi,

Yes, it just replicated when I plugged my laptop back into the second monitor and dragged Rubymine across to it.

N.

Error during dispatching of sun.awt.PeerEvent[INVOCATION_DEFAULT,runnable=apple.awt.EventFactoryProxy$2@699bf1,notifier=null,catchExceptions=false,when=1228271588055] on frame1: 1
java.lang.ArrayIndexOutOfBoundsException: 1
    at apple.awt.CWindow.displayChanged(CWindow.java:449)
    at apple.awt.EventFactoryProxy$2.run(EventFactoryProxy.java:84)
    at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
    at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
    at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.java:472)
    at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:465)
    at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:337)
    at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
    at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184)
    at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:176)
    at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)

Yes, it just replicated when I plugged my laptop back into the second monitor and dragged Rubymine across to it.

Nicholas,

You can notice from stacktrace that it is internal Java problem on MacOS. I got such error once, but after I restarted my Mac the problem went away.