Bug 196255

Summary:	Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
Product:	[Eclipse Project] Platform	Reporter:	JohnnySu <ntsjun>
Component:	SWT	Assignee:	Silenio Quarti <Silenio_Quarti>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	dj.houghton, steve_northover
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description JohnnySu

2007-07-11 22:31:50 EDT

Build ID: I20070621-1340

Steps To Reproduce:
1.&#22312;Eclipse&#20013;&#21551;&#21160;JAVA&#24212;&#29992;&#31243;&#24207;&#21518;&#19981;&#20570;&#20219;&#20309;&#25805;&#20316;
2.&#31561;&#35745;&#31639;&#26426;&#36827;&#20837;&#23631;&#20445;&#29366;&#24577;&#21518;&#65292;&#20877;&#38543;&#20415;&#21160;&#19968;&#19979;&#40736;&#26631;&#25110;&#38190;&#30424;
3.&#36825;&#26102;&#21018;&#25165;&#22312;Eclipse&#21551;&#21160;&#30340;JAVA&#24212;&#29992;&#31243;&#24207;&#25511;&#21046;&#21488;&#20250;&#20986;&#29616;&#36825;&#26679;&#30340;&#24322;&#24120;&#65306;
  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)
&#36825;&#20010;&#24322;&#24120;&#22312;3.2&#29256;&#26412;&#30340;Eclipse&#20013;&#23601;&#26377;&#36807;

More information:

Comment 1 Eric Moffatt

2007-07-17 10:06:09 EDT

Sorry, your 'steps' are unreadable...can you translate??

Comment 2 JohnnySu

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

2007-07-25 14:03:21 EDT

Yes, maybe a VM problem. Perhaps SWT has insight?

Comment 4 JohnnySu

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

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

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.