Re: exception in at javax.swing.SwingGraphics.createSwingGraphics

jobs239@xxxxxxxxxxx wrote in message news:<1121798481.050084.189240@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>...
> I am getting the following exception sometimes in my GUI. How can I
> debug this? There is nothing from my code in the stack and the
> exception is not easily reproducible. Any help will be greatly
> appreciated.
>
> java.lang.Exception: Stack trace
> at java.lang.Thread.dumpStack(Thread.java:1064)
> at
> javax.swing.SwingGraphics.createSwingGraphics(SwingGraphics.java:147)
> at javax.swing.JComponent._paintImmediately(JComponent.java:4670)
> at javax.swing.JComponent.paintImmediately(JComponent.java:4488)
> at
> javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:410)
> at
> javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:117)
> at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
javax.swing.SwingGraphics?
What is it?

> at
> java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
> at
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
> at
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
> at
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
> java.lang.NullPointerException
> at javax.swing.JComponent._paintImmediately(JComponent.java:4671)
> at javax.swing.JComponent.paintImmediately(JComponent.java:4488)
> at
> javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:410)
> at
> javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueueUtilities.java:117)
> at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:454)
> at
> java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:201)
> at
> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151)
> at
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:145)
> at
> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:137)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:100)
> In paintImmediately null graphics
.

Relevant Pages

  • Re: Difference between Debug and Release compilation?
    ... What I *do* see is that you're getting an exception that states that you are attempting an operation that is not implemented in the object you're trying to use. ... Based on what little stack trace you did post, it appears that some audio input source is having it's "enabled" state changed and that the source in question doesn't support changing that state. ... But that in no way answers why it works in Debug and not in Release. ... You posted in a different message that it works if your UserControl is Debug but your application is Release and that from that you conclude that the problem is in a third-party DLL. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Need Help Debugging
    ... you should use straight and plain ADPlus.VBS from the debugger package. ... debug info loaded, etc... ... does that avoid using the stack ?!? ... which is our custom CRITICAL_SECTION class. ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Difference between Debug and Release compilation?
    ... The full stack trace might be useful, ... But that in no way answers why it works in Debug and not in Release. ... All I can say is that you should be thankful you're getting an exception. ... You posted in a different message that it works if your UserControl is ...
    (microsoft.public.dotnet.languages.csharp)
  • [PATCH] i386: get rid of the use of KPROBE_ENTRY / KPROBE_END
    ... * Debug traps and NMI can happen at the one SYSENTER instruction ... * that sets up the real kernel stack. ... * a debug fault, and the debug fault hasn't yet been able to ...
    (Linux-Kernel)
  • Re: tracking down error in MFC42.dll
    ... It will belp as you will have the stack to look at. ... sure that it wouldn't happen in Debug. ... Currently I put a new version out that has proper try/catch blocks around ... to throw an exception in a test DLL with some hacked code and it did hang ...
    (microsoft.public.vc.mfc)