JDK-6638153 : Java Console crash with new OOPP
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 6u10
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows
  • CPU: x86
  • Submitted: 2007-12-06
  • Updated: 2010-04-04
  • Resolved: 2007-12-06
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6u10Resolved
Related Reports
Duplicate :  
Description
build tested - 6u10 jre b08 from the following location
/net/koori/onestop/jdk/6u10/promoted/ea/b08/bundles/windows-i586

Enable the next generation java plugin

Invoke the following applet in IE browser
http://sqeweb.sfbay.sun.com/deployment2/jitu/plug-bug/ALC/JOptionPaneTest.html

Java Console gets killed whenever the applet is reloaded (most of the times) with the following exception.
Note - This behavior is not there with old Plugin. 
Exception in thread "AWT-EventQueue-2" java.lang.NullPointerException: null pData
	at sun.awt.windows.WFramePeer.getState(Native Method)
	at sun.awt.windows.WEmbeddedFramePeer.getState(Unknown Source)
	at java.awt.Frame.getExtendedState(Unknown Source)
	at java.awt.Frame.getState(Unknown Source)
	at java.awt.Frame.removeNotify(Unknown Source)
	at java.awt.Window$1DisposeAction.run(Unknown Source)
	at java.awt.Window.doDispose(Unknown Source)
	at java.awt.Window.dispose(Unknown Source)
	at sun.awt.AppContext$4.run(Unknown Source)
	at java.awt.event.InvocationEvent.dispatch(Unknown Source)
	at java.awt.EventQueue.dispatchEvent(Unknown Source)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.awt.Container$2.run(Unknown Source)
	at java.awt.event.InvocationEvent.dispatch(Unknown Source)
	at java.awt.EventQueue.dispatchEvent(Unknown Source)
	at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
	at java.awt.EventDispatchThread.run(Unknown Source)

Comments
EVALUATION This is caused by fragility in the AWT and is not a bug in the plug-in. The AWT issue is being tracked under 6592751 and this bug is being closed as a duplicate of that one.
06-12-2007