Note that there are some explanatory texts on larger screens.

plurals
  1. POJava applet in firefox linux makes Java application launcher crash/exit
    primarykey
    data
    text
    <p>I have a Java applet that downloads data from where it's hosted, using HTTP. The applet has default permissions for an applet, that is, not many. Randomly during download, maybe 90% chance of reproductibility, at a specific part of the log, the <code>java</code> executable hosted by Firefox will exit abruptly, and the Java Console will be closed.</p> <p>I thought it was my first JVM crash after just a few weeks of Java, but could not find the Fatal Error Log. Until I found out that when Chromium is used to open the applet, it works 100% (many tries in various conditions, alterning with Firefox)</p> <p>Both browsers execute use the same commandlines for the <code>java</code> executable</p> <pre><code>Firefox: /usr/lib/jvm/java-6-sun-1.6.0.26/jre/bin/java -D__jvm_launched=20972388862 -Xbootclasspath/a:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/deploy.jar:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/javaws.jar:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/plugin.jar -Djava.class.path=/usr/lib/jvm/java-6-sun-1.6.0.26/jre/classes -Dsun.awt.warmup=true sun.plugin2.main.client.PluginMain write_pipe_name=/tmp/.com.sun.deploy.net.socket.5712.287531591049678510.AF_UNIX Chromium: /usr/lib/jvm/java-6-sun-1.6.0.26/jre/bin/java -D__jvm_launched=20858056974 -Xbootclasspath/a:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/deploy.jar:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/javaws.jar:/usr/lib/jvm/java-6-sun-1.6.0.26/jre/lib/plugin.jar -Djava.class.path=/usr/lib/jvm/java-6-sun-1.6.0.26/jre/classes -Dsun.awt.warmup=true sun.plugin2.main.client.PluginMain write_pipe_name=/tmp/.com.sun.deploy.net.socket.5428.6724684151611746860.AF_UNIX </code></pre> <p>Then I booted a Windows 2000 partition and also noticed that the applet was working 100% with the same version of Firefox and JRE. Could not try Chrome, not available on this platform.</p> <p>Now <strong>I'm not necessarily asking for a solution</strong> as my 'client' will use Windows 2000 to run the applet. I was posting this to know if someone experimented with java crashes could find an explanation to this. Is it the communication between Firefox Linux and <code>java</code> that could make <code>java</code> exit? If you had to make this work, how would you proceed? Try to produce an SSCCE for Mozilla?</p> <p>Versions: </p> <pre><code>Firefox 9.0.1 (both on Linux and Windows 2000) Chromium 9.0.597.45 (70550) Built on Debian 6.0, running on Debian 6.0.2 java version "1.6.0_26" Java(TM) SE Runtime Environment (build 1.6.0_26-b03) Java HotSpot(TM) Client VM (build 20.1-b02, mixed mode, sharing) </code></pre> <hr> <p><strong>EDIT</strong>: I found more information. When listening to Firefox's stderr, running the applet and then exiting Firefox after <code>java</code> exits, I get this. Not so useful though, it just tends to show that Firefox didn't even know that <code>java</code> exited.</p> <pre><code>Exception in thread "main" netscape.javascript.JSException: Plugin instance for applet ID 1 was already released at sun.plugin2.main.server.LiveConnectSupport.getInfo(LiveConnectSupport.java:405) at sun.plugin2.main.server.LiveConnectSupport.shutdown(LiveConnectSupport.java:41) at sun.plugin2.main.server.JVMInstance.unregisterApplet(JVMInstance.java:1300) at sun.plugin2.main.server.JVMInstance.recycleAppletID(JVMInstance.java:385) at sun.plugin2.main.server.JVMManager.recycleAppletID(JVMManager.java:316) at sun.plugin2.main.server.MozillaPlugin.stopApplet(MozillaPlugin.java:325) at sun.plugin2.main.server.MozillaPlugin.destroy(MozillaPlugin.java:225) </code></pre>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload