Comment 11 for bug 323110

Revision history for this message
In , Jon-vanalten (jon-vanalten) wrote :

I've tried this several more times. Managed to crash firefox once. Unfortunately didn't run from the command line that time....

However, I have come to realize something about what happens when it 'times out'. The web site goes to a page indicating applet timed out, however the applet keeps on running (java process using high CPU) for some time before ending. Tried running from the command line and the applet seems to terminate normally, and at the end spits out a URL whose page indicates satisfactory test results. Not sure yet why the browser believes it has timed out and doesn't get sent to the URL generated.

I have occasionally had the applet simply fail to load, with output along the lines of:

<SNIP>
net.sourceforge.jnlp.LaunchException: Fatal: Initialization Error: Could not initialize applet.
        at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:495)
        at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:441)
        at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:620)
Caused by: java.lang.NullPointerException
        at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:481)
        ... 2 more
Caused by:
java.lang.NullPointerException
        at net.sourceforge.jnlp.Launcher.createApplet(Launcher.java:481)
        at net.sourceforge.jnlp.Launcher.getApplet(Launcher.java:441)
        at net.sourceforge.jnlp.Launcher$TgThread.run(Launcher.java:620)
java.lang.NullPointerException
        at net.sourceforge.jnlp.NetxPanel.runLoader(NetxPanel.java:102)
        at sun.applet.AppletPanel.run(AppletPanel.java:380)
        at java.lang.Thread.run(Thread.java:636)
java.lang.NullPointerException
        at sun.applet.AppletPanel.run(AppletPanel.java:430)
        at java.lang.Thread.run(Thread.java:636)
</SNIP>

I've also been trying this with Sun's Java, and the timeout and failure to load issues happen there too (albeit with less frequency).

I suppose I should mention that all of this is using Firefox 3.5.