Red Hat Bugzilla – Bug 108684
IBM JRE doesn't ever stop running when used as plugin for Moz.
Last modified: 2008-07-13 23:33:52 EDT
Description of problem:
Once you link the gcc3 version of libjavaplugin_oji.so in
/usr/lib/mozilla-1.4/plugins Java plugins work. But once java loads, it never
goes away. If you kill it (even -15), Mozilla dies....
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. cd /usr/lib/mozilla-1.4/plugins
2. ln -s > /opt/IBMJava2-141/jre/bin/libjavaplugin_ojigcc3.so libjavaplugin_oji.so
3. Start Moz.
4. Goto any site w/ a Java plug.
5. Leave site forever.
6. ps -ef |grep java
7. kill -15 java_pid
Java stay running and when killed it kills Moz.
I'd expect it to have some timeout in Moz. (like Konq.) for when the Java
interpreter should be shutdown if it doesn't itself.
One more thing. If you let it run, it doesn't really eat up anymore
resources (other than the memory it already holds), it doesn't chew up
CPU. BUT it doesn't let anything else run either without a reload of
the page w/ the new applet.
The Java process stays running in the background so that the
performance penalty associated with JVM startup is incurred only once
per browser run. Otherwise the JVM would need to be restarted every
time a page containing an applet were loaded or reloaded.
What do you mean by "doesn't let anything else run"? Can you describe
a scenario in which you've seen this behaviour?
Ok, I guess I'm used to Konq's behavior of killing the java process.
On the latter case. During a fresh session goto a java applet page.
Leave that page and go to any other, the new one says it's running in
the Moz. status bar but isn't. You have to hit reload at which point
it really starts running. See what I mean? Cheers, -Ali
Somewhere along the way the problem was fixed or wasn't a core
problem. It's working clear-as-day now. Closing bug.