Closed Bug 215061 Opened 22 years ago Closed 20 years ago

Java applet which utilizes threads behaves erratically

Categories

(Core Graveyard :: Java: OJI, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: pschmandra, Assigned: joshua.xia)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1 I'm not sure if this is a bug or my programming, but the same applet rips using the Micro $oft virtual machine. Basically, a thread in the main applet waits for all the label threads to die before it enables the "Generate" button. This prevents people from clicking the button like a mad man. Solved it by simply enabling the "Generate" button from the label thread when it's finished and doing away with the thread in the main applet. It works but this method is not very elegant. BTW - I never managed to get bmp's to show up. I don't want to file a bug just to have a hundred people jump on my head just because it's a licensing issue or something. BMP's work fine with M$. Reproducible: Always Steps to Reproduce: 1. Load the applet 2. Press the "Generate Super Happy Luck Lotto Numbers" Actual Results: Numbers tumble in an erratic fashion. Expected Results: Numbers should tumble smoothly
please mention JRE used. Using Mozilla 2003080105 on Linux + Sun's JRE 1.4.2, applet never finishes loading and Java Console shows: java.lang.NullPointerException at sun.plugin.viewer.LifeCycleManager.startAppletPanel(Unknown Source) at sun.plugin.viewer.MNetscapePluginObject.startPlugin(Unknown Source) at sun.plugin.viewer.MNetscapePluginObject$Initer.run(Unknown Source) java.lang.ClassFormatError: NPDS/npDSEvtObsProxy (Truncated class file) at java.lang.ClassLoader.defineClass0(Native Method) at java.lang.ClassLoader.defineClass(Unknown Source) at java.security.SecureClassLoader.defineClass(Unknown Source) at sun.applet.AppletClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.applet.AppletClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.applet.AppletClassLoader.loadCode(Unknown Source) at sun.applet.AppletPanel.createApplet(Unknown Source) at sun.plugin.AppletViewer.createApplet(Unknown Source) at sun.applet.AppletPanel.runLoader(Unknown Source) at sun.applet.AppletPanel.run(Unknown Source) at java.lang.Thread.run(Unknown Source)
I'm using Sun Microsystems JVM 1.4.1_01 with firebird but I can't find a java console on this browser. The applet manages to load fine but it behaves erratically when the numbers tumble. When I load it using the MS JVM, no exceptions are showing up in the IE java console and it works great.
I just Loaded the applet in MS Explorer using Sun's plugin and got this exception thrown. java.lang.NullPointerException at sun.java2d.pipe.DrawImage.copyImage(Unknown Source) at sun.java2d.pipe.DrawImage.copyImage(Unknown Source) at sun.java2d.pipe.ValidatePipe.copyImage(Unknown Source) at sun.java2d.SunGraphics2D.drawImage(Unknown Source) at sun.java2d.SunGraphics2D.drawImage(Unknown Source) at CLlabel.paint(CLlabel.java) at sun.awt.RepaintArea.paint(Unknown Source) at sun.awt.windows.WComponentPeer.handleEvent(Unknown Source) at java.awt.Component.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.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source)
There is a NullPointerException in the Applet that for some reason MS JVM fails to throw. Looks like this is a bug in MS JVM not Sun's.
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.