Open dbanet opened 10 years ago
I can confirm that I see the same bahaviour
Even this genuine test doesn't work: https://www.java.com/en/download/installed.jsp. I get 100% CPU load as well. Will look at it.
Still digging through the logs in order to understand what causes a hang/crash. I see some differences in the protocol; FF 24 definitely uses a different order of things even when using plugins in old, in-process way.
I got another idea. There is IcedTea-Web 1.5 out (we have 1.3). So I will try to quickly update our plugin it to see if it helps.
JFYI. While updating the plugin to 1.5.1 I recalled and reported one significant subversion problem we have, see here: http://mantis.smedley.id.au/view.php?id=625.
It looks like making IcedTea-Web 1.5.1 build requires more time than we have now — there has been some incompatible changes since 1.3. I created a Java ticket for that: http://trac.netlabs.org/java/ticket/230.
Actually, I'm not really sure we should continue with this issue w/o first updating the plugin to 1.5.1 as there has been some work regarding the plugin hangs when running as in-process and out-of-process. See http://icedtea.classpath.org/wiki/IcedTea-Web#Plugin_hangs_Firefox and http://icedtea.classpath.org/wiki/Fixing_IcedTea-Web_Browser_Hanging for more info.
In particular, they claim that using the Java plugin in in-process mode may cause hangs and that may be the reason why it crashes in our case. And they also claim that it should work more or less OK in out-of-proces mode — in our case it hangs here but that may be caused by some issues in our IPC implementation.
Anyway, it's better to update to 1.5.1 first so that we don't have to work around potential 1.3 issues related to this problem and instead work around 1.5.1 issues if there are any.
this issue goes along with issue #7
I'm using the latest Firefox 24 public beta, the latest OpenJDK for OS/2 and the latest libodin.
If
dom.ipc.plugins.enabled
is set to true, then two CPUs get loaded up to 100% constnatly (until I close the browser), but the page gets displayed after two-three minutes (without the plugin of course).If
dom.ipc.plugins.enabled
is set to false, then Firefox crashes instantly.I've been told to provide some links to sites where Java applets do not work and cause the above to happen. Here they are:
But that doesn't matter; I was unable to make any Java applet on any site work.