Closed Bug 212280 Opened 22 years ago Closed 20 years ago

Reload very often and fast a page that contains 2 Java-Applets produces a NullPointerException

Categories

(Core Graveyard :: Java: OJI, defect)

Product:
Core Graveyard
Component:
Java: OJI
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED EXPIRED

People

(Reporter: Frank.Jiranek, Assigned: joshua.xia)

References

(
URL
)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.4) Gecko/20030624 Reload a Page that contains 2 Java-Applets (which were void in my example, no Methods implemented) very often (about 10-30 times) and fast using the Reload- Button of the Browser produces a JVM-Exception: java.lang.NullPointerException at sun.plugin.viewer.LifeCycleManager.startAppletPanel (LifeCycleManager.java:182) at sun.plugin.viewer.WNetscapePluginObject.startPlugin (WNetscapePluginObject.java:391) at sun.plugin.viewer.WNetscapePluginObject$Initer.run (WNetscapePluginObject.java:308) If you want to get the sources, just use: http://www.ep.haufe.de/~jiranek/StartAppletBug The example is very simple: The voidApplet.html contains 2 applet-tags: <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows- 1252"> <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> <meta name="ProgId" content="FrontPage.Editor.Document"> <title>voidApplet</title> </head> <body> <applet code="voidApplet.class" hspace="0" width="16" height="16"></applet> <applet code="voidApplet.class" hspace="0" width="16" height="16"></applet> </body> </html> And the Java-Applet voidApplet.java contains: import java.applet.Applet; public class voidApplet extends Applet { } Reproducible: Sometimes Steps to Reproduce: 1. Load the URL http://www.ep.haufe.de/~jiranek/StartAppletBug/voidApplet.html 2. Open Java-Console 3. Press the Browsers-Reload-Button very often and fast 4. => java.lang.NullPointerException Actual Results: A java.lang.NullPointerException occures. Expected Results: No Exceptions. My Testing Environment is win2k-SP3,Mozilla 1.4 and Suns-JVM 1.4.1_02 My PC: Pentium(R) 4 processor based system Processor speed 1,60 GHz Bus speed 400 MHz Board model Genuine Intel(R) D845WN system board OS version Windows* 2000 version 5.0 Service Pack 3 build 2195
confirming using build 2003070308 on Win2k + JRE 1.4.2.
Assignee: idk → joshua.xia
Component: Java-Implemented Plugins → OJI
QA Contact: avm → dsirnapalli
I see the same kind of problem with unix mozilla (Hardware=OS=ALL). This started happening recently (last few weeks). Mozilla/5.0 (X11; U; OSF1 alpha; en-US; rv:1.5b) Gecko/20030811 File (plugin131_01.trace) is created in my login directory. It currently contains this (traceback) information: Java(TM) Plug-in: Version 1.3.1_01 Using JRE version 1.3.1 Fast VM User home directory = /usr/users/jim ... Exception occurred during event dispatching: java.lang.NullPointerException: string is null at sun.java2d.SunGraphics2D.drawString(java.lang.String,int,int) (SunGra phics2D.java:2242) (pc 11) at Time.paint (Time.java:79) (pc 42) at sun.awt.RepaintArea.paint (RepaintArea.java:298) (pc 207) at sun.awt.motif.MComponentPeer.handleEvent (MComponentPeer.java:353) (p c 41) at java.awt.Component.dispatchEventImpl (Component.java:2663) (pc 504) at java.awt.Container.dispatchEventImpl (Container.java:1213) (pc 42) at java.awt.Component.dispatchEvent (Component.java:2497) (pc 2) at java.awt.EventQueue.dispatchEvent (EventQueue.java:339) (pc 36) at java.awt.EventDispatchThread.pumpOneEventForHierarchy (EventDispatchT hread.java:131) (pc 72) at java.awt.EventDispatchThread.pumpEventsForHierarchy (EventDispatchThr ead.java:98) (pc 12) at java.awt.EventDispatchThread.pumpEvents (EventDispatchThread.java:93) (pc 3) at java.awt.EventDispatchThread.run (EventDispatchThread.java:85) (pc 9)
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.