P4
FULL PRODUCT VERSION :
java version "1.6.0_12-ea"
Java(TM) SE Runtime Environment (build 1.6.0_12-ea-b03)
Java HotSpot(TM) 64-Bit Server VM (build 11.2-b01, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Linux rand 2.6.28-4-generic #5-Ubuntu SMP Fri Dec 26 22:48:55 UTC 2008 x86_64 GNU/Linux
EXTRA RELEVANT SYSTEM CONFIGURATION :
Ubuntu 8.10 Intrepid
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.5) Gecko/2008121623 Ubuntu/8.10 (intrepid) Firefox/3.0.5
A DESCRIPTION OF THE PROBLEM :
I am testing out the new 64-bit plugin. The root cause of the confusion is the fact that the plugin is located in JRE/lib/amd64/ and not in JRE/plugin/amd64/ (and I had to google around for directions on installing the plugin)
If you make a copy of the ".so" file into the firefox plugins directory, instead of a symbolic link, the plugin throws an assertion failure which kills the entire browser (and in one case caused the entire X Server to hang until firefox was kill -9.
The assertion failure was due to the fact that the JVM was not in the same directory as the shared object file, however the assertion was printed to the console so was not visible the first time I tried it (nor was it obvious that a java plugin on some website was the cause, since it crashed immediately)
I have no java-related environment variables set (not JAVA_HOME or anything)--the only way to determine the path to the JDK is via the symbolic links in update-alternatives.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Copy "/usr/local/jre/lib/amd64/libnpjp2.so" into "/usr/lib/firefox-addons/plugins/"
2. Go to a website with a java plugin.
3. Firefox crashes with a message on the console (pasted below) only if you are lucky enough to have run firefox from a console.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Since I gave the DLL no way to determine the java path, an acceptable result would be a single dialog box (once in the life of the browser) telling me that it does not know the path to the JRE, and subsequent attempts to load a java plugin would simply fail.
Some other plugins act this way if they fail to load.
Another (not as acceptable but better) alternative would be not to register the plugin at all (though that ends up being very confusing since I won't know why it failed to load).
ACTUAL -
The browser crashes with no indicator of what caused the crash (did not think it was java-related at first). Luckily firefox is able to reload the tabs from the previous session.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
...
Didn't find JVM under /usr/lib/firefox-addons/plugins
firefox: ../../../../src/plugin/solaris/plugin2/common/JavaVM.c:104: InitializeJVM: Assertion `foundJVM' failed.
zsh: abort firefox
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Use a symbolic link for the browser plugin (or ensure that appropriate environment variables are set):
ln -s "/usr/local/jre/lib/amd64/libnpjp2.so" "/usr/lib/firefox-addons/plugins/"
java version "1.6.0_12-ea"
Java(TM) SE Runtime Environment (build 1.6.0_12-ea-b03)
Java HotSpot(TM) 64-Bit Server VM (build 11.2-b01, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Linux rand 2.6.28-4-generic #5-Ubuntu SMP Fri Dec 26 22:48:55 UTC 2008 x86_64 GNU/Linux
EXTRA RELEVANT SYSTEM CONFIGURATION :
Ubuntu 8.10 Intrepid
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.5) Gecko/2008121623 Ubuntu/8.10 (intrepid) Firefox/3.0.5
A DESCRIPTION OF THE PROBLEM :
I am testing out the new 64-bit plugin. The root cause of the confusion is the fact that the plugin is located in JRE/lib/amd64/ and not in JRE/plugin/amd64/ (and I had to google around for directions on installing the plugin)
If you make a copy of the ".so" file into the firefox plugins directory, instead of a symbolic link, the plugin throws an assertion failure which kills the entire browser (and in one case caused the entire X Server to hang until firefox was kill -9.
The assertion failure was due to the fact that the JVM was not in the same directory as the shared object file, however the assertion was printed to the console so was not visible the first time I tried it (nor was it obvious that a java plugin on some website was the cause, since it crashed immediately)
I have no java-related environment variables set (not JAVA_HOME or anything)--the only way to determine the path to the JDK is via the symbolic links in update-alternatives.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Copy "/usr/local/jre/lib/amd64/libnpjp2.so" into "/usr/lib/firefox-addons/plugins/"
2. Go to a website with a java plugin.
3. Firefox crashes with a message on the console (pasted below) only if you are lucky enough to have run firefox from a console.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Since I gave the DLL no way to determine the java path, an acceptable result would be a single dialog box (once in the life of the browser) telling me that it does not know the path to the JRE, and subsequent attempts to load a java plugin would simply fail.
Some other plugins act this way if they fail to load.
Another (not as acceptable but better) alternative would be not to register the plugin at all (though that ends up being very confusing since I won't know why it failed to load).
ACTUAL -
The browser crashes with no indicator of what caused the crash (did not think it was java-related at first). Luckily firefox is able to reload the tabs from the previous session.
ERROR MESSAGES/STACK TRACES THAT OCCUR :
...
Didn't find JVM under /usr/lib/firefox-addons/plugins
firefox: ../../../../src/plugin/solaris/plugin2/common/JavaVM.c:104: InitializeJVM: Assertion `foundJVM' failed.
zsh: abort firefox
REPRODUCIBILITY :
This bug can be reproduced always.
CUSTOMER SUBMITTED WORKAROUND :
Use a symbolic link for the browser plugin (or ensure that appropriate environment variables are set):
ln -s "/usr/local/jre/lib/amd64/libnpjp2.so" "/usr/lib/firefox-addons/plugins/"