Bug 196255 - Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
Summary: Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Silenio Quarti CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-11 22:31 EDT by JohnnySu CLA
Modified: 2019-09-06 16:09 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description JohnnySu CLA 2007-07-11 22:31:50 EDT 
Build ID: I20070621-1340

Steps To Reproduce:
1.在Eclipse中启动JAVA应用程序后不做任何操作
2.等计算机进入屏保状态后，再随便动一下鼠标或键盘
3.这时刚才在Eclipse启动的JAVA应用程序控制台会出现这样的异常：
  Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
	at sun.awt.Win32GraphicsEnvironment.displayChanged(Win32GraphicsEnvironment.java:109)
	at sun.awt.windows.WToolkit$4.run(WToolkit.java:706)
	at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
	at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
这个异常在3.2版本的Eclipse中就有过

More information:
Comment 1 Eric Moffatt CLA 2007-07-17 10:06:09 EDT 
Sorry, your 'steps' are unreadable...can you translate??
Comment 2 JohnnySu CLA 2007-07-24 21:31:56 EDT 
1 When I launching a application server developed by ourself in eclipse
2 Don't tounch the computer until the screen savers occur.
3 Then press any key of the keyboard 
4 This following Exception  will occured in the console of eclipse 
  Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
        at
sun.awt.Win32GraphicsEnvironment.displayChanged(Win32GraphicsEnvironment.java:109)
        at sun.awt.windows.WToolkit$4.run(WToolkit.java:706)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
        at
java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
        at
java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
        at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
        at
java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
5 The developing environment is 
         JDK 1.5.0_12 , eclipse 3.3.0 Build id: I20070621-1340 
When I launching this server in JProfiler ,this exception occured again. so maybe it is caused by JDK .
sorry , I'm not sure you will unstand what I presented, because my English is poor.(In reply to comment #1)
> Sorry, your 'steps' are unreadable...can you translate??
> 

(In reply to comment #1)
> Sorry, your 'steps' are unreadable...can you translate??
>
Comment 3 DJ Houghton CLA 2007-07-25 14:03:21 EDT 
Yes, maybe a VM problem. Perhaps SWT has insight?
Comment 4 JohnnySu CLA 2007-07-25 22:11:19 EDT 
(In reply to comment #3)
> Yes, maybe a VM problem. Perhaps SWT has insight?
> 
No, this is just a console application .But the java.awt.MediaTracker has been used to crop and composite image.
Comment 5 Steve Northover CLA 2007-08-14 13:02:21 EDT 
This looks like a Sun problem.  It should be possible to construct code that uses java.awt.MediaTracker and cause the NullPointerException.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:09:23 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.