Java exception on minimalize/maximalize


    Jun 24 2009 | 12:47 pm
    Dear board,
    Recently I've been getting Java errors in my Max window. Took me a while to find out when, but it appears to happen when I minimalize or maximalize ANY window, even for example the finder window. It doesn't matter whether Max loses or gains focus from this or not.
    This doesn't start right away from the moment I start Max, but rather after 'a while' of patching, but I haven't found when exactly. It continues to happen when I close all patches too. It does disappear when I restart Max. I think it may have been happening since I installed the Java update just this week.
    There are a couple Java objects in my patch (that I don't know that much about, other than that they seem to work), but can they have anything to do with this? Seems far-fetched as the error continues after closing the patch. Has anyone else had anything like this? Here's the error:
    Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at apple.awt.CGraphicsEnvironment.resetDisplays(CGraphicsEnvironment.java:99) at apple.awt.CGraphicsEnvironment.displayChanged(CGraphicsEnvironment.java:49) at apple.awt.CToolkit$4.run(CToolkit.java:1310) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:461) 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)
    Thanks, Bas.

    • Feb 25 2010 | 11:15 am
      Yes, I have this as well. Also without Java-objects in the patch that I'm working on.
      The errors just appear, sometimes when I'm working in Max, other times when Max is open but I'm working in another application.
      Using OS X 10.5.8, Max/MSP 5.1.3, Java 1.5.0 (I think)
      I will try updating the Java runtime to see if that helps.
    • Feb 26 2010 | 9:03 am
      Solved: Updated my Java runtime.