Closed Bug 133029 Opened 23 years ago Closed 23 years ago

JAVA Plugin exception when entering print preview of example URL

Categories

(Core :: Print Preview, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

VERIFIED DUPLICATE of bug 122048

People

(Reporter: dave, Assigned: rods)

References

()

Details

When using print preview on the Stadplandienst URL attached to this report, the java plugin in mozilla 0.9.9 pc crashes reproducable with the following stack trace: java.lang.NullPointerException: null pData at sun.awt.windows.WFramePeer.getState(Native Method) at java.awt.Frame.getState(Unknown Source) at java.awt.Frame.removeNotify(Unknown Source) at java.awt.Window$1$DisposeAction.run(Unknown Source) at java.awt.Window.dispose(Unknown Source) at sun.plugin.navig.win32.PluginFrame.windowClosing(Unknown Source) at java.awt.Window.processWindowEvent(Unknown Source) at java.awt.Window.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) This was on win2k 5.0.2195 sp2 + security update, with the current Java SDK 1.4 + plugin. After that crash, mozilla does not work anymore and can't be restarted unless the mozilla process is removed with task manager. Since it is a java exception, unfortunately no talkback data is generated.
Resolving as a duplicate. Reporter, if you believe that this is not a duplicate, feel free to reopen the bug. *** This bug has been marked as a duplicate of 122048 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.